Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upNo auto-completion for macro results #338
Comments
This comment has been minimized.
This comment has been minimized.
|
This is a problem with Racer, which is embedded in the RLS. I don't think there is anything actionable here - Racer can't be made to understand macros, but eventually we will use the compiler instead. |
nrc
closed this
Jun 12, 2018
This comment has been minimized.
This comment has been minimized.
JeanMertz
commented
Aug 11, 2018
Thanks for this. Being new to rust, I like learning a language through exploration, and auto-completion in my editor makes it possible for me to gradually go down the rabbit hole of the standard library and what I can do with what type. Hitting this while working on some toy code, I was also confused by this. I am curious to hear if there's some kind of up-to-date roadmap on what has already been done on the compiler side to support this (or basically all RLS features), and what still has to be done? |
This comment has been minimized.
This comment has been minimized.
JeanMertz
commented
Aug 11, 2018
•
|
Also a quick follow-up. Is this the same reason why the following doesn't work? Any way to find out what works, and what doesn't work (aside from trying, but then I'm wondering if I should file a bug report, or not)? I looked over in the Racer repository, but couldn't find anything in the documentation about this. |
This comment has been minimized.
This comment has been minimized.
lnicola
commented
Aug 30, 2018
|
@JeanMertz your latter sample isn't a macro, so you should probably file an issue. |


Noah11012 commentedJun 12, 2018
When using a macro such as
vec!and then trying to call a method on the vector, no auto-completion comes up.Code: