Marek Kaput
Marek Kaput
When something fails in project model code, send a notification to the user instead of just logging an error. See all TODO comments that look like this one: https://github.com/starkware-libs/cairo/blob/0f0f721f3f9d28f56cc519c4277fde67d0d03934/crates/cairo-lang-language-server/src/lib.rs#L583
The project model should primarily be triggered by opening workspaces instead of opening files. https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_workspaceFolders https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeWorkspaceFolders The ultimate goal would be that opening files won't be necessary in E2E tests....
As title says, `LsSemanticGroup` is the better place for these functions
Primarily, calling `scarb metadata` should be an asynchronous process that does not block project model updates like it does currently. ## Requirements * This is a good opportunity to drop...
Research how we should deal with projects/crates that are renamed/removed. What should happen regarding them in `AnalysisDatabase` inputs?
Split `FilesGroup` into 4 traits/query groups: 1. `InputGroup: FilesPrototype` that takes all non-file-related inputs & interns (crate configs, cfg_sets, flags etc.) (crate `cairo-lang-filesystem`) 2. `FilesPrototype` which will be a trait...
@Draggu please fill this issue description with precise information what are the problems and how we can fix them. cc #6141
All Salsa queries, used in `AnalysisDatabase` must have a set sensible LRU policy to keep memory usage limited. Check out how this is done in Rust Analyzer for reference. https://github.com/salsa-rs/salsa/blob/754eea8b5f8a31b1100ba313d59e41260b494225/book/src/rfcs/RFC0004-LRU.md...