Incorrect warning: missing reference: code_warntype

[mroavi]

@code_warntype is exported by default.

The following warning is displayed whenever I use this macro:

[pfitzseb]

Pretty sure that's correct unless you explicitly import InteractiveUtils, no (in which case I don't see the missing reference warning)?

[mroavi]

Ohh You are right @pfitzseb. I just realized that I'm importing InteractiveUtils in my startup.jl. Isn't it possible for LanguageServer to be aware of the usings in startup.jl?
At this moment, I'm able to use @code_warntype while this warning is displayed.

[pfitzseb]

InteractiveUtils is also automatically loaded in the REPL.
Imho linting is most useful for self-contained pieces of code (with its own environment, ideally), so I don't think we should ever look at startup.jl.

[mroavi]

I removed using InteractiveUtils from my startup.jl and I still see the warning.

[pfitzseb]

Yes, sure. There's no connection between the file you're currently in and startup.jl, so of course this shows up as unresolved. Why shouldn't it?

[mroavi]

Ok. I think I understand what you mean: InteractiveUtils is not exported by default like e.g. Base. It is actually being loaded by the REPL at startup. And the REPL is just one way of running Julia code.

So the solution to avoid the unwanted warning is to add using InteractiveUtils on the top of the file that is attached to the LSP server, is this right?

[pfitzseb]

Yes. You'd need to do that for a self-contained/portable script anyways.

[mroavi]

I'ts clear now. Thanks @pfitzseb .