Option for import path when re-exports exist — preferences/excludes

[maeldroem]

Use case

A crate (lib) I'm working on provides a global prelude module, from which programmers can quickstart the usage of the crate by doing crate_name::prelude::*;.

Internally though, I want to avoid relying on the prelude re-exports, and choose their original location instead and makes those imports independent from changes to the prelude's re-exports.

Unfortunately, completion suggestions from rust-analyzer will always suggest the shortest path to an item that is not yet imported.

Potential solutions

1. Option to ignore re-exports
2. Option to ignore a list of modules' re-exports
3. Option to ignore a list of specific re-exports
4. Option to enable prompting for disambiguation when multiple paths to an item in the same crate exist
5. Option to "canonicalize" an import (i.e. "rephrase" an import path that uses a re-export to an import path to the original location of the item)

Thank you for considering this feature :)

PS: May be related to #20468 , but I'm not certain that it's about the same thing, as they talk more about external modules rather than internal re-exports.

[ChayimFriedman2]

I think r-a should avoid prelude imports where possible when "rust-analyzer.imports.preferPrelude": false. That will help with this issue.