-
Notifications
You must be signed in to change notification settings - Fork 13k
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
#132594
Subtree update of rust-analyzer
#132594
Conversation
No idea how this slipped past me
By removing interior mutability from it.
Cleanup TypeRef lowering
fix: Fix the server not honoring diagnostic refresh support
Do not render meta info when hovering usages
feat: Add assist to generate a type alias for a function
fix: auto-complete import for aliased function and module
…p-document docs: create setup documentation
I don't like the party of `bool`s that is becoming, but two isn't worth a refactoring yet IMO.
fix: Only parse `safe` as contextual kw in extern blocks
This requires some serious code juggling.
Publish test-fixture => ra_ap_test_fixture
Move `child_by_source` from `hir-def` to `hir`
…erctx Avoid interior mutability in `TyLoweringContext`
Parse patterns with leading pipe properly in all places
Allow interpreting consts and statics with interpret function command
…casing minor: Fix feature name casing
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`
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#132153 (Stabilise `const_char_encode_utf16`.) - rust-lang#132355 (Fix compiler panic with a large number of threads) - rust-lang#132486 (No need to instantiate binder in `confirm_async_closure_candidate`) - rust-lang#132594 (Subtree update of `rust-analyzer`) r? `@ghost` `@rustbot` modify labels: rollup
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 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (fbab782): comparison URL. Overall result: ✅ improvements - 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 1.0%, secondary -0.1%)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.
CyclesResults (secondary -3.2%)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 780.381s -> 780.214s (-0.02%) |
r? @ghost