Joshua Batty
Joshua Batty
After solving a bug in #6575 that was crashing the server on did save events, I noticed that we do not return any diagnostics to the user. Iv'e played around...
see these comments from #6555 https://github.com/FuelLabs/sway/pull/6555/files#r1762715435 & https://github.com/FuelLabs/sway/pull/6555/files#r1764155422
The below screen shot is from the examples/arrays project. 
## Description This PR relaxes version constraints across the crate's dependencies. ## Changes: * Updated version constraints for all dependencies to use minor version specifications instead of patch versions *...
## Description Doing some general code quality changes at the same time. ## Checklist - [ ] I have linked to any relevant issues. - [ ] I have commented...
We were having this problem with the `did_open_all_std_lib_files` test but it was dramatically sped up with #7215 I'm surprised this test takes so long to complete even with those optimisations...
Currently we only support a single workspace in the LSP server. In the sway repo there are multiple workspaces each with their own workspace members. This is a pretty common...
I suspect this will involve a similar process to getting vim support.
Currently, `sway-lsp` creates separate sessions with duplicated state (like `Engines` and `TokenMap`) for each member within a workspace, leading to inefficiency. This issue tracks the effort to refactor the language...
This is a follow on from #7079 At the moment we are spawning a tokio thread to watch for changes to the projects `Forc.toml` file. This isn't very effecient, we...