Re:Rust's 2017 roadmap, six months in
by MichaelGG on Wednesday July 05, 2017 @06:58PM
(#14706819)
Is seems that Racer is still missing support for auto-complete on basic code snippets:
Even if they special cased vec! or all the std macros, it'd be a good on-ramp improvement. But I thought RLS was supposed to step in where Racer can't handle things - is that not the case for macro support?
[ Parent
| on HN ]
> Is seems that Racer is still missing support for auto-complete on basic code snippets
Interesting; I view that as a bit more than a "basic" snippet for autocompletion to handle, although that's mostly a few facto interpretation because it's one of the few things that no Rust autocompletion engine I've tried (racer, RLS, or Intellij's plugin) has been able to handle. For pretty much everything else I've tried, at least one of them has been able it.
Well I mean it's basic in the sense of it's a common piece of code a beginning might write in the first few minutes with Rust.
Fair enough! I definitely agree with you there
Re:Rust's 2017 roadmap, six months in
by steveklabnik on Wednesday July 05, 2017 @07:18PM
(#14706964)
You said racer above; did you mean to say the RLS?
The linked article mentions that RLS completes via Racer, which is inline with what I understood before: Racer's a lot faster for this use-case, so RLS delegates to it.
Re:Rust's 2017 roadmap, six months in
by steveklabnik on Wednesday July 05, 2017 @07:49PM
(#14707140)
Yes, my confusion is that in your OP, you were talking a bunch about racer, but then switched to the RLS.
Right now, it's exactly what you said. RLS is still an extremely active project, and so are the compiler internals it relies on, so it's going to gain features in the future. I'm not aware of any specific plans to exclude macros, but it's not my area of specialty.