include! concat! env! OUT_DIR not auto completing

[chinedufn]

Hey!

I tried to use the latest nightly of rust-analyzer (as of approximately May 15) within VSCode to see if I could get auto complete for some constants that were generated in a build.rs.

The rust-analyzer tests suggest that it works in main.rs - and I'm seeing it work when I create a new project and try to auto-complete within main.rs.

As soon as I start to stray from that I lose auto-complete.

For example, if I move the include! call to mod bindings and type bindings:: I can no longer auto complete the constants.

Is this a known limitation at this time - or am I perhaps misconfigured? I have the setting to check out dirs on startup turned on.

I could whip up an example project (or rust-analyzer test case if you can point me into the right direction?) if needed - but as far as I can tell as soon as you start trying to import include!d types from other modules the auto complete stops working.

Thanks and cheers!

---

$ rustc -V
rustc 1.45.0-nightly (2454a68cf 2020-05-04)

[edwin0cheng]

Did you enable : rust-analyzer.cargo.loadOutDirsFromCheck ? It is off by default .

[chinedufn]

Yup sure did ! I checked the check box in the VSCode rust-analyzer extension settings.

Not sure if it matters, but I originally ran into this in my project’s cargo workspace but I verified that I get the same issues in a non workspace as well.

[edwin0cheng]

I could whip up an example project

Yeah, a minimal reproducible example will be nice to have to help here. !

[chinedufn]

Sure!

Everything is captured in the attached screenshot. I expected the pictured auto-complete to include GENERATED_CONSTANT.

Here's a repository with the code above: https://github.com/chinedufn/rust-analyzer-issue-4482

[flodiebold]

Hm, could it be a problem with relative paths, since the path inside the generated_constants module will be relative to src/generated_constants? 🤔

[chinedufn]

@flodiebold thanks for the help! Sorry, I'm not quite getting what you're asking?

[flodiebold]

I'm just speculating about the reason for the bug 😉

[chinedufn]

@edwin0cheng anything happen to ring a bell in terms of what might be happening?

Cheers!

[edwin0cheng]

No idea, and this week I am a bit busy, but I think I will be investigating this weekend.

[chinedufn]

Awesome - no rush at all - thanks!

[edwin0cheng]

Oh , I just tested it in master(00172d0) and it works:

[chinedufn]

@edwin0cheng just upgraded to the latest nightly and that example works for me!

However, here's an example that does not work:

I would expect the generated_constants module to be in the suggestions (the constants aren't auto completed either).

I've updated the reproduction repository with the code in this screenshot.

[edwin0cheng]

Um.. It works for me too :

You may need to reload the VSCode after adding tests folder.

[chinedufn]

Ah nice that works!

So I'm still seeing issues in my real crate such as:

But I suppose I can open separate issues for them with reproducible examples.

I'll give it some time then come back to rust-analyzer in case the issue happens to resolve itself like this issue did (just to avoid trying to reproduce this).

Thanks so much!