Ali Afroozeh
Ali Afroozeh
I think in other REPLs the implicit variable names all stay in the scope when the REPL session is valid, so they should go to the top-level environment. As far...
Also would be good to drop semicolon requirement for statements as well. It's particularly noticeable when importing modules. This screenshot is from the Java REPL (JShell in Java 11).
Any updates on this issue? It would be nice to have portable .classpath files.
Recently, I'm also observing issues with `rust-analyzer.check.workspace" : false`. It just checks the current crate and all the dependent crates on it. In very deep crates, it takes quite some...
@alibektas I can confirm that it was not the case before, editing/save in that deep crate was immediate when `rust-analyzer.check.workspace` was `false`. Now, it seems like `true` or `false` value...
@alibektas my RustAnalyzer is up to date. if you're now running cargo check on the current crate and all dependent crates, it's going to be slow for live editing for...
I'm sorry, I meant RustAnalyzer, there is no RustRover, it was a typo 😅 (I updated the comment to avoid confusing for other readers)
> Let me get back to you with this in a few days. I am rewriting most of the cargo check logic. [alibektas](https://github.com/alibektas) Thank you. Please also make the semantic...
@alibektas is there any update on this issue?
The current `"rust-analyzer.check.workspace": false` is broken in the sense that it does not do `cargo check -p`. To me it seems like it checks the current package and all dependent...