How to ignore some path for auto-import

[A4-Tacks]

use core::convert::identity;

fn main() {
    identity(i$0)
}

Output completions:

identity(…)~ const fn(T) -> T           f [LS]
i8 i8                                   S [LS]
if~                                     k [LS]
i16 i16                                 S [LS]
i32 i32                                 S [LS]
i64 i64                                 S [LS]
i128 i128                               S [LS]
isize isize                             S [LS]
if let~                                 k [LS]
include                                 r [LS]
include_str                             r [LS]
include_bytes                           r [LS]
io(use std::os::unix::io)               M [LS]
id()~(use std::process::id) fn() -> u32 f [LS]
i16(use core::i16)                      M [LS]
i64(use core::i64)                      M [LS]
i8x2(use core::simd::i8x2)              S [LS]
isize(use core::isize)                  M [LS]
i16x1(use core::simd::i16x1)            S [LS]
i16x2(use core::simd::i16x2)            S [LS]
i16x8(use core::simd::i16x8)            S [LS]
i32x1(use core::simd::i32x1)            S [LS]
i32x8(use core::simd::i32x8)            S [LS]
i64x1(use core::simd::i64x1)            S [LS]
i64x4(use core::simd::i64x4)            S [LS]
i64x8(use core::simd::i64x8)            S [LS]
i8x16(use core::simd::i8x16)            S [LS]

How can I make auto-import ignore paths prefixed with core::simd in the config file?

[flodiebold]

Why do you want to do that?

[A4-Tacks]

I never use core::simd, but they always appear in the completion list and are annoying

[ChayimFriedman2]

https://rust-analyzer.github.io/book/configuration.html#completion.autoimport.exclude, although it doesn't allow to exclude all items in a module.

[A4-Tacks]

Can support it? Just like

"completion.autoimport.exclude": {
    "path": "core::simd",
    "type": "module"
}

[ChayimFriedman2]

Can? Probably yes. But I'm not sure we want it to. For example, what if you put std::simd in there, and suddenly it doesn't work because the types are only re-exported there?

[A4-Tacks]

Can simply write two ignore rules: "core::simd" and "std::simd"

[ChayimFriedman2]

Huh, even what you posted wouldn't work, because even in core it's a reexport. I bet that would be very confusing.

[ChayimFriedman2]

Can simply write two ignore rules: "core::simd" and "std::simd"

What do you mean? To never flyimport them? What if the user does want them?

[A4-Tacks]

What do you mean? To never flyimport them? What if the user does want them?

In user configuration file

[ChayimFriedman2]

Oh, you meant the user will ignore both. But how will the user know that's what they want? Unless they understand how r-a works, all they'd know is that they put it in the ignore list and it didn't work.

[A4-Tacks]

Perhaps it can be explained in the document that his behavior is very simple,
simply causing the auto-import to avoid a certain module path

[ChayimFriedman2]

The problem is that the full path is not something you can find in any way other than looking at the source code, and it also isn't guaranteed to be stable.

[A4-Tacks]

Can't I use the path in the completion list? like i32x1(use core::simd::i32x1) S [LS]

[ChayimFriedman2]

No, because that path is based on our find-path, which doesn't necessarily give the real path (e.g. it doesn't in this case).

[ShoyuVanilla]

Besides whether or not we might implement this on rust-analyzer, I guess you are using vim and maybe this could be filtered with vim scripting?