@matklad isn't the documentation missing inlay hints? and runnables?
Yup, and parent modules
just asking because the changelog says "all" ;)
I want to finish those tomorrow
That's changelog for Tuesday :P
(Also, sorry for breaking existing emacs command by rearranging some not-so-siginificant details. My hypothesis is that getting rid of
rust-analyzer specific prefixes, and just trying to make proper protocol extensions would lead to a better ecosystem long term)
yeah, I'm kind of waiting for you to be done to fix all the emacs stuff ;)
Hi, I am trying to debug lsp extension and after following guild in dubugging.md I am facing issue of "Ignored breakpoint because generated code not found". I have updated the launch.json file to add node_modules js files in outFiles. Then only facing issue.
How to solve this issue?
I am adding debug point in on_task() function.
I provided --sourceMap to npm build script in package.json, still it is not working. Any suggestions how to get debug point in main_loop.rs on_task() function?
I had already added
in rust analyzer settings.json file.
Did you change Cargo.toml ?
[profile.dev] debug = 2 # default is 0
Thank for the reply @vsrs .
Yes, I did that in crates/rust-analyzer/cargo.toml file and then build the project.
Is this file is right, or am I suppose to update any other file?
Also I have added those lines at the end of file. As in that file there was no existing entry for dev profile.
After searching profile.dev in project files, I updated the workspace cargo.toml file with dev = 2. Then also no luck.
I have attached debugger to rust-analyzer server also.
Any suggestions on this?
Go the debugging working. The solution is first run Run extension (Debug) and then attach server. while selecting rust analyzer server select debug path of rust analyzer. Hope this helps, if anyone is facing same issue.