{"action":"created","issue":{"url":"https://api.github.com/repos/phildawes/racer/issues/389","labels_url":"https://api.github.com/repos/phildawes/racer/issues/389/labels{/name}","comments_url":"https://api.github.com/repos/phildawes/racer/issues/389/comments","events_url":"https://api.github.com/repos/phildawes/racer/issues/389/events","html_url":"https://github.com/phildawes/racer/issues/389","id":104786003,"number":389,"title":"Detect Vec methods when using vec![]","user":{"login":"Wilfred","id":70800,"avatar_url":"https://avatars.githubusercontent.com/u/70800?v=3","gravatar_id":"","url":"https://api.github.com/users/Wilfred","html_url":"https://github.com/Wilfred","followers_url":"https://api.github.com/users/Wilfred/followers","following_url":"https://api.github.com/users/Wilfred/following{/other_user}","gists_url":"https://api.github.com/users/Wilfred/gists{/gist_id}","starred_url":"https://api.github.com/users/Wilfred/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wilfred/subscriptions","organizations_url":"https://api.github.com/users/Wilfred/orgs","repos_url":"https://api.github.com/users/Wilfred/repos","events_url":"https://api.github.com/users/Wilfred/events{/privacy}","received_events_url":"https://api.github.com/users/Wilfred/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/phildawes/racer/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-03T21:32:02Z","updated_at":"2015-09-25T02:12:56Z","closed_at":null,"body":"I've seen issues discussing autocomplete on macros and jumping to definitions, but I've also noticed that racer can't tell `vec![]` is of type `Vec`.\r\n\r\nAs a result, racer can't offer any completions here:\r\n\r\n```rust\r\nfn main() {\r\n    let m = vec![];\r\n    m.\r\n}\r\n```\r\n\r\neven though using an explicit `Vec` creation is fine:\r\n\r\n```rust\r\nfn main() {\r\n    let m = Vec::new();\r\n    m.\r\n}\r\n```"},"comment":{"url":"https://api.github.com/repos/phildawes/racer/issues/comments/143103888","html_url":"https://github.com/phildawes/racer/issues/389#issuecomment-143103888","issue_url":"https://api.github.com/repos/phildawes/racer/issues/389","id":143103888,"user":{"login":"echochamber","id":4073509,"avatar_url":"https://avatars.githubusercontent.com/u/4073509?v=3","gravatar_id":"","url":"https://api.github.com/users/echochamber","html_url":"https://github.com/echochamber","followers_url":"https://api.github.com/users/echochamber/followers","following_url":"https://api.github.com/users/echochamber/following{/other_user}","gists_url":"https://api.github.com/users/echochamber/gists{/gist_id}","starred_url":"https://api.github.com/users/echochamber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/echochamber/subscriptions","organizations_url":"https://api.github.com/users/echochamber/orgs","repos_url":"https://api.github.com/users/echochamber/repos","events_url":"https://api.github.com/users/echochamber/events{/privacy}","received_events_url":"https://api.github.com/users/echochamber/received_events","type":"User","site_admin":false},"created_at":"2015-09-25T02:12:56Z","updated_at":"2015-09-25T02:12:56Z","body":"@phildawes how difficult would it be to get autocompletion for external libraries that define types using macros (or impls traits  using macros). This is the feature I've missed most and it seems that if we could expand the macros and save the result somewhere, then we could just do autocompletion using the generated code.\r\n\r\nI have very little knowledge of programming language design, parsing, compilers ect... so this is all just based on general intuition. If this is a reasonable approach I'd be willing to take a crack at implementing it."}}