{"action":"created","issue":{"url":"https://api.github.com/repos/racket/racket/issues/1102","labels_url":"https://api.github.com/repos/racket/racket/issues/1102/labels{/name}","comments_url":"https://api.github.com/repos/racket/racket/issues/1102/comments","events_url":"https://api.github.com/repos/racket/racket/issues/1102/events","html_url":"https://github.com/racket/racket/pull/1102","id":113181559,"number":1102,"title":"Improve how multi-in assigns source location info for its expansion","user":{"login":"lexi-lambda","id":759911,"avatar_url":"https://avatars.githubusercontent.com/u/759911?v=3","gravatar_id":"","url":"https://api.github.com/users/lexi-lambda","html_url":"https://github.com/lexi-lambda","followers_url":"https://api.github.com/users/lexi-lambda/followers","following_url":"https://api.github.com/users/lexi-lambda/following{/other_user}","gists_url":"https://api.github.com/users/lexi-lambda/gists{/gist_id}","starred_url":"https://api.github.com/users/lexi-lambda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lexi-lambda/subscriptions","organizations_url":"https://api.github.com/users/lexi-lambda/orgs","repos_url":"https://api.github.com/users/lexi-lambda/repos","events_url":"https://api.github.com/users/lexi-lambda/events{/privacy}","received_events_url":"https://api.github.com/users/lexi-lambda/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-10-24T20:32:47Z","updated_at":"2015-10-25T00:03:36Z","closed_at":"2015-10-25T00:03:36Z","pull_request":{"url":"https://api.github.com/repos/racket/racket/pulls/1102","html_url":"https://github.com/racket/racket/pull/1102","diff_url":"https://github.com/racket/racket/pull/1102.diff","patch_url":"https://github.com/racket/racket/pull/1102.patch"},"body":"This changes how `multi-in` is implemented so that the location for each expanded element in the final `require` spec is tied to the last relevant module path element. This allows DrRacket to intelligently show arrows linking each imported binding with a relevant piece of the multi-in import spec.\r\n\r\nTo demonstrate how this looks in DrRacket, I've taken two screenshots:\r\n\r\n<img width=\"614\" alt=\"screen shot 2015-10-24 at 1 27 10 pm\" src=\"https://cloud.githubusercontent.com/assets/759911/10712583/13479e16-7a53-11e5-96a0-d45c2d36a06a.png\">\r\n<img width=\"614\" alt=\"screen shot 2015-10-24 at 1 27 30 pm\" src=\"https://cloud.githubusercontent.com/assets/759911/10712587/20698064-7a53-11e5-91e7-22e03288baac.png\">\r\n\r\nIn contrast, without this change, no syntax arrows whatsoever are displayed for any identifiers imported with `multi-in`."},"comment":{"url":"https://api.github.com/repos/racket/racket/issues/comments/150873103","html_url":"https://github.com/racket/racket/pull/1102#issuecomment-150873103","issue_url":"https://api.github.com/repos/racket/racket/issues/1102","id":150873103,"user":{"login":"stamourv","id":854429,"avatar_url":"https://avatars.githubusercontent.com/u/854429?v=3","gravatar_id":"","url":"https://api.github.com/users/stamourv","html_url":"https://github.com/stamourv","followers_url":"https://api.github.com/users/stamourv/followers","following_url":"https://api.github.com/users/stamourv/following{/other_user}","gists_url":"https://api.github.com/users/stamourv/gists{/gist_id}","starred_url":"https://api.github.com/users/stamourv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stamourv/subscriptions","organizations_url":"https://api.github.com/users/stamourv/orgs","repos_url":"https://api.github.com/users/stamourv/repos","events_url":"https://api.github.com/users/stamourv/events{/privacy}","received_events_url":"https://api.github.com/users/stamourv/received_events","type":"User","site_admin":false},"created_at":"2015-10-25T00:03:36Z","updated_at":"2015-10-25T00:03:36Z","body":"Merged, thanks!"}}