-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Subtree update of rust-analyzer
#143565
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
#143565
Conversation
…actory` Signed-off-by: Hayashi Mikihiro <[email protected]>
Signed-off-by: Hayashi Mikihiro <[email protected]>
…method_with_if_let_method-to-SyntaxFactory Migrate `replace_is_method_with_if_let_method` Assist to use `SyntaxFactory`
Signed-off-by: Hayashi Mikihiro <[email protected]>
…al_to_const-assist-tosyntaxeditor Migrate `promote_local_to_const` Assist to `SyntaxEditor`
Signed-off-by: Hayashi Mikihiro <[email protected]>
…o_delimiter Migrate `toggle_macro_delimiter` Assist to use `SyntaxEditor`
Signed-off-by: Hayashi Mikihiro <[email protected]>
…_cfg_attr-assist-to-syntaxeditor Migrate `wrap_unwrap_cfg_attr` Assist to use `SyntaxEditor`
… only if the link target is inferred That is, do it for `[macro foo]`, but not for `[macro foo](macro foo)`.
…-link fix: Remove keyword prefixes (`macro@` or `macro `) from links in the docs only if the link target is inferred
Restructure proc-macro loading erros, differentiate hard error property on kind
Workaround missing none group support in builtin macros
Re-enable fixpoint iteration for variance computation
fix: Do not warn about proc-macro srv when sysroot is missing
`--all-targets` coupled with `--compile-time-deps` will never actually build binaries and so it won't fail for targets where libtest is missing
Skip unnecessary `eq` work in `BodySourceMap`
Improve flycheck and build script progress reporting
Previously, the following configuration in settings.json: "rust-analyzer.workspace.discoverConfig": { "command": [ "oops", "develop-json", "{arg}" ], "progressLabel": "rust-analyzer", "filesToWatch": [ "BUCK", "TARGETS" ] }, Would previously cause a crash in rust-analyzer: thread 'LspServer' panicked at crates/rust-analyzer/src/main_loop.rs:776:84: called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" } Instead, use more specific panic messages.
They need to return `!`, unlike diverging ordinary assignments. See the comment in the code.
remove `rust-analyzer/syntaxTree` from docs
`hir_ty::match_check` cleanup: remove special handling for box patterns
…-assignment-never fix: Fix diverging destructuring assignments
…_projects fix: Avoid .unwrap() when running the discover command
Add AsMut, Borrow and BorrowMut to minicore and famous_defs
chore: Remove dead field from `InferenceContext`
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 |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing c720f49 (parent) -> 8df4a58 (this PR) Test differencesShow 4 test diffs4 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 8df4a58ac47b778b093652d6190a6f9d54638774 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (8df4a58): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.3%, secondary 2.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 464.259s -> 466.974s (0.58%) |
r? @ghost