I don't know what is happening to my rust-analyzer

[rafaelsmgomes]

Checked other resources

• This is not a bug report or feature request (Please use issues for those).
• This is a question about rustaceanvim, not rust-analyzer or Neovim.
• This is not a question about autocompletion.
• I have read the README.
• I have read the FAQ.
• I have searched for a solution using :h rustaceanvim.
• I have searched existing discussions.
• I have searched the existing issues/discussions of other plugins related to this question (if applicable).
• I have searched the existing rust-analyzer discussions (if applicable).
• I have added a very descriptive title to this question.

Description

I'm at my wits' end. I have been using nvim for years now and I've been coding in rust for work for the last 6 months.

I love what rustacean.nvim has to offer and I've been happily using it for a long time.

But I cannot find a solution to my problem and I don't even know what is wrong. I assure you I looked everywhere.

But alas, if I can't find a solution to this I can't be productive at work.

My problem is that rust-analyzer's lsp simply does not work with some functions.

Granted, these are usually related to diesel and I've read everywhere that diesel is notorious for having issues with rust-analyzer due to it's heavy usage of macros.

But here is what my rust code looks like:

Now, all of these errors are not truly errors. And I was shocked a few months ago when I learned that my co-worker, who is using VSCo** does not have these LSP issues.

So I tried using JetBrains IDE RustRover, and well:

It works, no problem.

What can I do to fix this? I have no idea.

This is my last ditch attempt to fix it by asking if someone has a clue. Help me not move from nvim, I beg you.

BTW: this is not a rustacean.nvim issue. This is an LSP issue. I have ditched rustacean.nvim to try and fix it. But it has persisted.
I did not know where else to post this since there isn't a nvim rust community online that I'm aware of.

I assure you I have tried every rust-analyzer config under the sun, and still the problems persist.

Example Code

...

Neovim version (nvim -v)

v0.11.4

Operating system/version

macOS 15.6.1

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim:                                                               ✅

Checking for Lua dependencies ~
- ✅ OK [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap) installed.

Checking external dependencies ~
- ✅ OK rust-analyzer: found rust-analyzer 0.3.2593-standalone (6b2e677795 2025-08-25)
- ✅ OK Cargo: found cargo 1.90.0 (840b83a10 2025-07-30)
- ✅ OK rustc: found rustc 1.90.0 (1159e78c4 2025-09-14)
- ✅ OK debug adapter: found codelldb 

Checking config ~
- ✅ OK No errors found in config.

Checking for conflicting plugins ~
- ✅ OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- ✅ OK tree-sitter parser for Rust detected.
- ✅ OK .vscode/settings.json loaded without errors.

[mrcjkb]

Hey 👋

I'd recommend you compare your rust-analyzer configuration (:checkhealth vim.lsp) with that of your coworker.

Also, see if you can reproduce it with the minimal config provided with this repo (see the troubleshooting section in the readme).

• If you can't, then you need to bisect your config and plugins.
• If you can, I can help if you provide a project that reproduces the issue.

[rafaelsmgomes]

Hey 👋!

I will try to create a project that reproduces this issue. I did try to configure it with mini.nvim to check that if I removed every other plugin, it would remain broken. It is still broken.... So I don't think is a conflict with other plugins.

I did try every single configuration for the rust-analyzer as I could think of. I got the same configuration used by default on VSCo**.

Alas, it did not work. I suspect it has to do with the fact that we are heavily using submodule at my work.
Something about how nested submodules are breaking rust-analyzer could be the issue.

I can't share the actual code where the problem is, since it is work code.

But thanks for the offer. I will try to create a project that reproduces it.

See if I nest submodules and use Diesel with it, if I can get it to break.

Will report back when I have done so.