[Need help] tauri auto completion is very slow

[GOKORURI007]

In the Tauri project, the auto-completion feature of Rust is extremely slow. It usually takes 1 to 3 seconds to display the possible completion results, whether in Rustover or in VSCode.

Are there any other people who have encountered this problem? Is there a solution?

[5h5ong]

I'm having same issue. My OS is Windows and I'm mainly using Cursor as my editor. This probably isn't related, but changing rust-analyzer's target-dir to target/analyzer didn't make any difference.

It's a similar situration even when tauri dev isn't running. It's same on both Cursor and Rustrover.

I found this answer, but I'm not sure if it's still relevant.
He speculates that Rustrover might struggle to handle projects like Tauri: #11736

I've kept looking, but I'm completely at a loss. Are other people also developing at this speed?

[FabianLars]

Back when i commented this the performance in vscode + rust-analyzer for example was much better though so it seemed like a RustRover specific problem. Something seems to have happened in the last few months or so seeing that we get reports from non RR users as well now.

[5h5ong]

Thank you for your reply.

Should I assume this is relatively recent issue? Along with auto-completion, I've noticed that the speed of updating errors and warnings is also slow.

I really enjoyed the feeling of writing code in Rust, so this is quite disappointing.

Would it help if I downgraded the version of rust-analyzer?

[FabianLars]

I think it's a relatively recent issue, yes. I can't tell whether it's rust-analyzer's fault or ours, I assume the latter but no clue.

Maybe if you can find rust-analyzer version from idk, the beginning of the year or something it'd be worth a try.

[NuclEnergy]

This seems to be a problem with the tauri::generate_context!() macro. I commented it out and it stopped slowing down, but I don't know what the problem is. I haven't seen any recent changes to the relevant code.

[FabianLars]

Yep exactly that's it. We couldn't spot what's causing it exactly yet either. v2 is much heavier on the macro die to permission system but this issue didn't start with the initial v2 release but much later...