-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Investigate completion and highlight performance #10369
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
A couple more: Profile
|
hey, i have contributed before and am interested in some perf investigation/improvement work. I can have a look at why descend_into_macros is slow on code outside a macro, would appreciate any tips on interpreting the profiler results and potential perf improvements. |
Note the function is not necessarily slow outside of macros, highlighting triggers over the entire file every time and the file in question here has a pretty big macro input. You should be able to test the file out by using it in an integrated benchmark in Also see the Zulip thread here https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/.60descend_into_macros.60.20seems.20slow |
thanks! Will have a look at the benchmark. aside - it's a shame rust-lang chooses a closed platform like zulip that requires a sign-up. |
The discussions are publicly available at https://zulip-archive.rust-lang.org/stream/185405-t-compiler/rust-analyzer/topic/.60descend_into_macros.60.20seems.20slow.html ... unfortunately, IMO. |
thanks! |
highlighting
|
Closing this as the cause for this specific issue has been addressed again mainly and completion performance is tracked in another issue. |
Highlight seems slow lately, possibly due to
descend_into_macros
, even on code outside macros. Example (repeatedly typing and removing a character at the end ofConfig::json_schema
incrates/rust-analyzer/src/config.rs
:The text was updated successfully, but these errors were encountered: