-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Debug test lens #3539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! Thank you for the awesome extension! It does help a lot to debug rust-analyzer tests itself! I personally don't see any impediments to merge the PoC, since |
Yup, we should just do that, thanks for exploring this @hdevalke! Although, impl-wise, I think we should try to avoid providing separate debug/run commands, and instead have a single command which can be both debugged and runed. Ie, instead of introducing |
We also should upstream this to the LSP/VS Code. There should be a proper protocol request for telling which things can be run from a given context.... |
Opened microsoft/language-server-protocol#944 upstream |
Hi @matklad, You are right sharing a common structure for debugging or running should work as well. The only difference between runnable and debug configuration is: I made a new commit using only the modified To make this user friendly there is probably some need to add vscode-lldb as an extension dependency, or show a popup to propose to install vscode-lldb if |
yes, it's fine to add vscode-lldb as a dependency of rust-analyzer |
3561: feat: add debug code lens r=matklad a=hdevalke Refs #3539 3577: Protect against infinite macro expansion in def collector r=edwin0cheng a=flodiebold Something I noticed while trying to make macro expansion more resilient against errors. There was a test for this, but it wasn't actually working because the first recursive expansion failed. (The comma...) Even with this limit, that test (when fixed) still takes some time to pass because of the exponential growth of the expansions, so I disabled it and added a different one without growth. CC @edwin0cheng Co-authored-by: Hannes De Valkeneer <[email protected]> Co-authored-by: hdevalke <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
I am the maintainer of the Rust Test Lens extension in vscode.
Issue 17 was created because it was not possible to debug crates that contain a
main.rs
and alib.rs
in the same project. I cannot solve that problem without parsing the rust code.As a proof of concept I tried to implement this in rust-analyzer see: hdevalke@2e2ad8c.
Do you think it makes sense to integrate this in
rust-analyzer
, knowing that currently it depends on the vscode-lldb extension?The text was updated successfully, but these errors were encountered: