Skip to content
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.

Bad autocompletion for iterators #627

Open
olehmisar opened this issue Jul 23, 2019 · 5 comments
Open

Bad autocompletion for iterators #627

olehmisar opened this issue Jul 23, 2019 · 5 comments

Comments

@olehmisar
Copy link

into_iter(), iter(), and iter_mut() methods on Vec<T>, [T; N] etc types return iterators. But autocompletion is missing for these iterators.

Screenshot_20

Screenshot_21

@jetpackpony
Copy link

I'm having the same issue

@dan-cooke
Copy link

dan-cooke commented Aug 19, 2019

Same issue for string literals

image

@jetpackpony
Copy link

I've researched the issue a bit and it seems that it's a part of a larger issue with how the rust compiler is at the moment. There is a discussion here: rust-lang/rls#6

@antonkulaga
Copy link

So any progress on this issue? It creates a lot of pain!

@SoptikHa2
Copy link

Irrelevant to the project itself, but rust-analyzer works perfectly and is great workaround. There are stability issues (it keeps crashing and restarting) and it uses a bit more processing power so I don't like using it as much as RLS, but it gets the work done. It has perfect type inference and works flawlessly with iterables, and pretty much everything I've thrown at it. It makes working with iterables completely different experience.

Install the rust-analyzer extension and change rust-client.engine to rust-analyzer in settings.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants