-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust autocomplete full path visibility #13494
Comments
Hey, thanks for filling this issue. This actually looks like a regression from #13043, as we don't read that field in Rust. Completions used to look as follows on last Stable: |
Awesome ! |
Updated to latest Preview Release. Now some of suggestions has module names, but not all. Not sure if it's expected behaviour. |
In doing so we get to surface origin packages more prominently. Fixes #13494 (again) Release Notes: - Fixed origin packages not being surfaced in Rust completions
OMG, it's so awesome ! |
@osiewicz I don't think this works as of |
Check for existing issues
Describe the feature
Rust autocomplete doesn't show full module path for suggestions, and when there are several options with same name it's hard to understand what will be added.
For example writing opening autocomplete for
Result
that might be added fromanyhow::Result
or other it's impossible to know whereResult
is from. The only way is to try to guess by docs, but it's also very hard.If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: