Renaming lib.rs to main.rs and vice versa breaks RLS

[KalitaAlexey]

Hi everybody.
Steps:

• Execute:

cargo new t

• Open VSCode (I used both vscode-rust and rls_vscode).
• Open the created project
• Rename lib.rs to main.rs
• Enter something
• RLS shows that analysis is performing, but no diagnostics are shown
• Rename main.rs to lib.rs
• Enter something
• RLS shows that analysis is performing and diagnostics are shown.

Note:
rls_vscode also shows the second status bar item "RLS Analysis".

[nrc]

Are you renaming the file in VSCode or outside? If inside, then I wonder if there is a notification we should be catching (and treating like 'on_change') that we currently ignore. If it is outside VSCode, there is probably nothing we can do about this for now.

[KalitaAlexey]

@nrc,
Inside VSCode.

[Xanewok]

@nrc with implemented Cargo rebuild on configuration change, we might start watching file changes now and rebuild on .rs/.toml file change - this should solve the issue for now, I think?

[nrc]

with implemented Cargo rebuild on configuration change, we might start watching file changes now and rebuild on .rs/.toml file change - this should solve the issue for now, I think?

Yes, indeed. I was thinking to only watch Cargo.toml/.lock though

[nrc]

We now watch Cargo.toml/.lock. I don't know if this is still a problem.

[Xanewok]

Unfortunately still seems to be an issue - the analysis is missing until a Cargo rebuild is performed (this impacts crate build graph). I think we should watch the added/removed .rs file and somehow figure out from there if we need to rebuild the entire project (model).