rust-analyzer | A Rust compiler front-end for IDEs

To those that come across this question, Rust Analyzer was not the actual issue here. Instead, there was another plugin cargo that was also performing checks and did not have the features specified. After uninstalling the plugin, everything worked fine.

The way I figured out that this was that it was this issue was by following the advice of @ChayimFriedman to analyze what was actually reporting the problem. Since nothing was claiming the error, it couldn't be Rust Analyzer, as when it reports errors, the source shows rust-analyzer. This led me to look into the other plugins installed.

The reason that top-level or-patterns aren't allowed is because it would cause certain macro_rules! macros to break. The pattern in a let expression should be matchable by a single $p:pat, but without requiring it to be parenthesized, a $p:pat would only consume the first part of the or-pattern.

Note that you can work around this easily, as the compiler suggests when you try this:

You need to explicitly state what the lifetime of the Trait Object &'dyn DefDatabase is so that the borrow checker knows what the lifetime of any references held by the struct behind the pointer are. 'static is the default if you do not define it, or it cannot otherwise be determined from the context. See default trait object lifetimes in the rust language reference for more information.

Adding a lifetime to your Upcast trait definition allows you to drop 'static.

Just disable overflow checking for tests in your Cargo.toml file:

Update rustc to fix this and ensure that Visual Studio Code uses the correct Rust compiler.

1. Run rustup update to update rustc
2. Check version used by rust-analyzer: Ensure that ctrl+p -> Rust Analyzer: Show RA Version shows rust-analyzer version: 183ef048f 2021-11-22 stable.
3. Run cargo clean to clear obsoleted compiler output
4. Close all VS Code windows and open them again.

This should fix the issue. If not, have a look here.

In Visual Studio Code you can easily do this.

1. Open the settings page (Ctrl+,)
2. Search for "rust-analyzer inlay"
3. Uncheck things you don't want
   • In your case that would be "Parameter Hints" and "Type Hints"

If you're not using Visual Studio Code you'll need to manually edit the JSON config file of rust-analyzer (helpful link to the documentation). Basically

1. Open the JSON config file in your favourite text editor
2. Add a new property to the root of the JSON object like so:

Unfortunately, the ext_contract proc macro is only aware of the code within that block, and cannot generate code based on the methods of the Supertrait definition of NonFungibleTokenCore here https://github.com/roshkins/sputnik-dao-contract/blob/bc8398257cdbee248fdd6301af0dc41a9b7c5236/sputnik-nft-staking/src/lib.rs#L18.

For now, you would have to redefine the interface, but I will ask around if there is a cleaner way to do this.

Something like this might solve your immediate problem:

It is possible to fix it with rustfix but according to github issue, this lint is filtered out, it can be included via setting env var(ref).

for Windows:

You could try using this extension pack (it contains the extension Language Support for Java(TM) by Red Hat that gives the information you're looking for when hovering over Java code):

Make sure to also have tooltips enabled. You can read about enabling them here.