about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2025-07-06Auto merge of #143507 - matthiaskrgr:rollup-lpg7t12, r=matthiaskrgrbors-476/+1469
Rollup of 6 pull requests Successful merges: - rust-lang/rust#143238 (Port `#[ignore]` to the new attribute parsing infrastructure) - rust-lang/rust#143441 (Stop using `Key` trait unnecessarily) - rust-lang/rust#143478 (Miri subtree update) - rust-lang/rust#143486 (remove armv5te-unknown-linux-gnueabi target maintainer) - rust-lang/rust#143489 (Complete rustc_ast::mut_visit for spans.) - rust-lang/rust#143494 (Remove yields_in_scope from the scope tree.) r? `@ghost` `@rustbot` modify labels: rollup
2025-07-06Merge pull request #20175 from dianne/match-check-box-cleanupChayim Refael Friedman-60/+20
`hir_ty::match_check` cleanup: remove special handling for box patterns
2025-07-06Auto merge of #143126 - dianqk:update-llvm, r=nikicbors-0/+0
Update LLVM submodule Fixes rust-lang/rust#140686, fixes rust-lang/rust#141913, fixes rust-lang/rust#142752, fixes rust-lang/rust#143399.
2025-07-06cargo updategithub-actions-2/+2
compiler & tools dependencies: Locking 6 packages to latest compatible versions Adding io-uring v0.7.8 Updating jsonpath-rust v1.0.2 -> v1.0.3 Updating libffi v4.1.0 -> v4.1.1 Updating libffi-sys v3.3.1 -> v3.3.2 Updating tokio v1.45.1 -> v1.46.1 Updating wasm-component-ld v0.5.14 -> v0.5.15 note: pass `--verbose` to see 41 unchanged dependencies behind latest library dependencies: Locking 0 packages to latest compatible versions note: pass `--verbose` to see 4 unchanged dependencies behind latest rustbook dependencies: Locking 1 package to latest compatible version Updating cc v1.2.27 -> v1.2.29
2025-07-06Always bump in the parser in `err_and_bump()`Chayim Refael Friedman-8/+50
Even when at curly braces, otherwise the parser can get stuck. This has happened in the past in #18625, but it was just worked around instead of handling the root of the problem. Now this happened again in #20171. IMO we can't let `err_and_bump()` not bump, that's too confusing and invites errors. We can (as I did) workaround the worse recovery instead.
2025-07-05clippy: conditions are no longer wrapped in `DropTemps`dianne-48/+29
2025-07-05Rollup merge of #143486 - husqvarnagroup:af/no-armv5te-target-maintainer, ↵Matthias Krüger-1/+1
r=petrochenkov remove armv5te-unknown-linux-gnueabi target maintainer Sadly my former employer doesn't want to maintain this any more and I have no personal interest in maintaining it.
2025-07-05Rollup merge of #143478 - RalfJung:miri-sync, r=RalfJungMatthias Krüger-475/+1468
Miri subtree update r? `@ghost`
2025-07-05bootstrap: add change_tracker entry for removal of spellcheck:fixbinarycat-0/+5
2025-07-05compiletest: print slightly more information on fs::write failureRalf Jung-1/+2
2025-07-05Fix diverging destructuring assignmentsChayim Refael Friedman-2/+61
They need to return `!`, unlike diverging ordinary assignments. See the comment in the code.
2025-07-06restructure try_run_testsbit-aloo-18/+13
2025-07-05Rollup merge of #143447 - jieyouxu:compiletest-maintenance-4, r=KobzolBen Kimock-93/+353
[COMPILETEST-UNTANGLE 4/N] Improve compiletest config documentation This is part of a patch series to untangle `compiletest` to hopefully nudge it towards being more maintainable. This PR should contain **no functional changes**. This is pulled out to its own PR to make follow-up changes easier to review. There are *intentionally* a *lot* of FIXME comments, intended to be gradually addressed in follow-ups. r? `@Kobzol`
2025-07-05tidy: add specific error message for trying to use `spellcheck:fix`.binarycat-0/+7
2025-07-05tidy: use --bless for tidy spellcheck instead of spellcheck:fixbinarycat-6/+5
previous behavior was inconsistent with existing extra checks.
2025-07-05Fix Borrow and BorrowMut define from beta stdA4-Tacks-2/+2
2025-07-05Auto merge of #143474 - jieyouxu:bootstrap-llvm-snapshot, r=Kobzolbors-0/+8
Pretend in bootstrap snapshot tests that we always build in-tree LLVM Otherwise, depending on whether CI LLVM is inhibited or if an externally-provided LLVM is used, bootstrap host LLVM build step could be missing in step snapshots. Note that I'm not sure if this is the *right* solution (this might be *a* solution). I imagine we do want to control for the set of configuration that these snapshot tests are run, as much as possible. r? `@Kobzol`
2025-07-05remove armv5te-unknown-linux-gnueabi target maintainerAdrian Friedli-1/+1
2025-07-05Merge pull request #4444 from devnexen/filemetadata_updRalf Jung-4/+22
shims::fs adding more fields to FileMetadata
2025-07-05minor cleanupRalf Jung-9/+4
2025-07-05Auto merge of #143473 - workingjubilee:rollup-bxie7zg, r=scottmcmbors-39/+39
Rollup of 11 pull requests Successful merges: - rust-lang/rust#142440 (`tests/ui`: A New Order [14/N]) - rust-lang/rust#143040 (Add `const Rem`) - rust-lang/rust#143086 (Update poison.rs to fix the typo (sys->sync)) - rust-lang/rust#143202 (`tests/ui`: A New Order [18/N]) - rust-lang/rust#143296 (`tests/ui`: A New Order [21/N]) - rust-lang/rust#143297 (`tests/ui`: A New Order [22/N]) - rust-lang/rust#143299 (`tests/ui`: A New Order [24/N]) - rust-lang/rust#143300 (`tests/ui`: A New Order [25/N]) - rust-lang/rust#143397 (test passing a `VaList` from rust to C) - rust-lang/rust#143410 (Block SIMD in transmute_immediate; delete `OperandValueKind`) - rust-lang/rust#143452 (Fix CLI completion check in `tidy`) r? `@ghost` `@rustbot` modify labels: rollup
2025-07-05shims::fs adding more fields to FileMetadataDavid Carlier-4/+27
addressing, partially at least, FIXME comment and targetting unixes, adding device, user and group ids.
2025-07-05miri-script: set msrv so clippy doesn't suggest too-new featuresRalf Jung-2/+1
2025-07-05Improve compiletest config documentationJieyou Xu-93/+353
Including a bunch of FIXMEs.
2025-07-05fmtRalf Jung-1/+3
2025-07-05Merge from rustcRalf Jung-51/+121
2025-07-05Preparing for merge from rustcRalf Jung-1/+1
2025-07-05Pretend in bootstrap snapshot tests that we always build in-tree LLVMJieyou Xu-0/+8
2025-07-04always check for mixed deref pattern and normal constructorsdianne-0/+8
This makes it work for box patterns and in rust-analyzer.
2025-07-04`hir_ty::match_check`: remove special handling for box patternsdianne-60/+20
2025-07-05Auto merge of #139598 - compiler-errors:no-bound-var-symbol, r=WaffleLapkinbors-47/+49
Remove `Symbol` from `Named` variant of `BoundRegionKind`/`LateParamRegionKind` The `Symbol` is redundant, since we already store a `DefId` in the region variant. Instead, load the name via `item_name` when needed (which is almost always on the diagnostic path). This introduces a `BoundRegionKind::NamedAnon` which is used for giving anonymous bound regions names, but which should only be used during pretty printing and error reporting.
2025-07-04Rollup merge of #143452 - Kobzol:completions-fix, r=jieyouxuJubilee-35/+39
Fix CLI completion check in `tidy` The list of CLI completion files that were generated and that were checked by `x test tidy` was not synced. Recently, some PR only updated some of the files, which caused the rest of the files (not checked by `x test tidy`) to be dirty on `master`. This PR fixes the logic in bootstrap to always synchronize the list of completion paths. Fixes: https://github.com/rust-lang/rust/issues/143451 r? `@jieyouxu`
2025-07-04Rollup merge of #142440 - Kivooeo:tf14, r=tgross35Jubilee-4/+0
`tests/ui`: A New Order [14/N] > [!NOTE] > > Intermediate commits are intended to help review, but will be squashed prior to merge. Some `tests/ui/` housekeeping, to trim down number of tests directly under `tests/ui/`. Part of rust-lang/rust#133895. r? `@jieyouxu`
2025-07-05make mark_as_executed privatebit-aloo-17/+5
2025-07-05migrate render test to new bootstrap command streaming API'sbit-aloo-11/+7
2025-07-05migrate cargo streaming to new bootstrap command streaming API'sbit-aloo-14/+11
2025-07-05add streaming command struct for (spawn + piping scenario)bit-aloo-10/+64
2025-07-05Rollup merge of #143372 - cjgillot:bare-glob-map, r=petrochenkovMatthias Krüger-1/+1
Remove names_imported_by_glob_use query. Based on https://github.com/rust-lang/rust/pull/143247 r? ``@ghost`` for perf
2025-07-04Update completionsJakub Beránek-3/+3
2025-07-04Unify completion list between `x test tidy` and `x run generate-completions`Jakub Beránek-32/+36
2025-07-04remote-test-client: Exit code `128 + <signal-number>` instead of `3`Martin Nordholts-1/+3
If the remote process is terminated by a signal, make `remote-test-client` exit with the code `128 + <signal-number>` instead of always `3`. This follows common practice among tools such as bash [^1]: > When a command terminates on a fatal signal whose number is N, Bash uses the > value 128+N as the exit status. It also allows us to differentiate between `run-pass` and `run-crash` ui tests without special case code in compiletest for that when `remote-test-client` is used. [^1]: https://www.gnu.org/software/bash/manual/html_node/Exit-Status.html
2025-07-04Port `#[non_exhaustive]` to the new attribute parsing infrastructureJonathan Brouwer-13/+19
2025-07-04Same for typesMichael Goulet-2/+3
2025-07-04Remove Symbol for Named LateParam/Bound variantsMichael Goulet-45/+46
2025-07-04remove syntaxTree from docsvinícius x-18/+0
2025-07-04fix: Avoid .unwrap() when running the discover commandWilfred Hughes-3/+8
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.
2025-07-04Update LLVM submoduledianqk-0/+0
2025-07-04Rollup merge of #143420 - Kobzol:rdg-push, r=jieyouxuMatthias Krüger-18/+72
rustc-dev-guide subtree update Subtree update of https://github.com/rust-lang/rustc-dev-guide. Created using https://github.com/rust-lang/josh-sync. r? `@jieyouxu`
2025-07-04Rollup merge of #143387 - dpaoliello:shouldpanicfn, r=bjorn3Matthias Krüger-13/+8
Make __rust_alloc_error_handler_should_panic a function Fixes rust-lang/rust#143253 `__rust_alloc_error_handler_should_panic` is a static but was being exported as a function. For most targets this doesn't matter, but Arm64EC Windows uses different decorations for exported variables vs functions, hence it fails to link when `-Z oom=abort` is enabled. We've had issues in the past with statics like this (see rust-lang/rust#141061) but the tldr; is that Arm64EC needs symbols correctly exported as either a function or data, and data MUST and MUST ONLY be marked `dllimport` when the symbol is being imported from another binary, which is non-trivial to calculate for these compiler-generated statics. So, instead, the easiest thing to do is to make `__rust_alloc_error_handler_should_panic` a function instead. Since `__rust_alloc_error_handler_should_panic` isn't involved in any linking shenanigans, I've marked it as `AlwaysInline` with the hopes that the various backends will see that it is just returning a constant and perform the same optimizations as the previous implementation. r? `@bjorn3`
2025-07-04Rollup merge of #143286 - Muscraft:track-diagnostics-note, r=WaffleLapkinMatthias Krüger-3/+5
Make -Ztrack-diagnostics emit like a note [#t-compiler/diagnostics > Rendering -Ztrack-diagnostics like a note](https://rust-lang.zulipchat.com/#narrow/channel/147480-t-compiler.2Fdiagnostics/topic/Rendering.20-Ztrack-diagnostics.20like.20a.20note/with/526608647) As discussed on the Zulip thread above, I want to make `-Ztrack-diagnostics` emit like a `note`. This is because I find its current output jarring, and the fact that it gets rendered completely left-aligned, [even in the middle of a snippet](https://github.com/rust-lang/rust/blob/86e05cd300fac9e83e812c4d46582b48db780d8f/tests/ui/track-diagnostics/track6.stderr), seems like something that should be changed. Turning it into a `note` seems like the best choice, as it would align it with the rest of the output, and `note` is already used for somewhat similar things, like seeing why a lint was fired. --- Note: turning `-Ztrack-diagnostics` into a `note` will also make `annotate-snippets` API a bit cleaner
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 22:29:41 +0000