-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Subtree update of rust-analyzer
#134377
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
Subtree update of rust-analyzer
#134377
Conversation
Previously all lints were assumed to be `#[warn]`, and we had a hand-coded list of `#[allow]` exceptions. Now the severity is autogenerated from rustdoc output. Also support lints that change status between editions, and the `warnings` lint group.
Fix publish workflow link in manual
…everity Properly handle different defaults for severity of lints
…le_with_no_snippet fix: Generate implementation with items even if snippet text edit is disabled
fix: copied proc-macros not being cleaned up on exit
fix: Fix sourceroot construction for virtual manifests
internal: Only parse the object file once in proc-macro-srv
feat: Add an assist to extract an expression into a constant
internal: Drop proc-macro server support for ~1.66.0 and older toolchains
Corrected the spelling of "defererence" to "dereference" in the error message that informs users about invalid casting requirements.
Fix typo in error message for invalid casting
fix: Panic when displaying generic params with defaults, again
internal: Implement `naked_asm!` builtin
minor: Bump typos
…nges fix: Revert changes to client capabilities in `bac0ed5`
internal: Show mir eval errors on hover with debug env var set
fix: Fix proc-macro dylib names on windows
rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
@bors r+ p=1 subtree sync |
Subtree update of `rust-analyzer` r? `@ghost`
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry network error? |
☀️ Test successful - checks-actions |
Finished benchmarking commit (83ab648): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -2.7%, secondary 0.6%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 770.216s -> 770.694s (0.06%) |
r? @ghost