about summary refs log tree commit diff
path: root/tests
AgeCommit message (Collapse)AuthorLines
2025-06-23rustdoc-json: Add test for `#[cold]`Alona Enraght-Moony-0/+3
Follow-up to https://www.github.com/rust-lang/rust/pull/142491
2025-06-23Enable reproducible-build-2 for WindowsDaniel Paoliello-11/+25
2025-06-23Account for beta revisions when normalizing versionsJosh Stone-8/+8
Several UI tests have a `normalize-stderr` for "you are using x.y.z" rustc versions, and that regex is flexible enough for suffixes like "-nightly" and "-dev", but not for "-beta.N". We can just add '.' to that trailing pattern to include this.
2025-06-23Rollup merge of #142923 - folkertdev:min-function-alignment-no-attributes, ↵Jubilee-4/+6
r=workingjubilee fix `-Zmin-function-alignment` on functions without attributes tracking issue: https://github.com/rust-lang/rust/issues/82232 related: https://github.com/rust-lang/rust/pull/142854 The minimum function alignment was skipped on functions without attributes (because the logic was in a loop that only runs if there is at least one attribute). The underlying reason we didn't catch this before is that in our testing we generally apply `#[no_mangle]` to functions that are tested. I've added a test now that deliberately has no attributes. r? `@workingjubilee`
2025-06-23Rollup merge of #142873 - Urgau:issue-139830, r=BoxyUwUJubilee-2/+32
Don't suggest changing a method inside a expansion Fixes https://github.com/rust-lang/rust/issues/139830 r? compiler
2025-06-23Port `#[rustc_skip_during_method_dispatch]` to the new attribute systemPavel Grigorenko-0/+114
2025-06-23[Arm64EC] Only decorate functions with `#`Daniel Paoliello-1/+55
2025-06-23Add `#[loop_match]` for improved DFA codegenbjorn3-0/+1425
Co-authored-by: Folkert de Vries <folkert@folkertdev.nl>
2025-06-23compiletest: Improve diagnostics for line annotation mismatchesVadim Petrochenkov-35/+138
2025-06-23fix `-Zmin-function-alignment` without attributesFolkert de Vries-4/+6
the minimum function alignment was skipped on functions without attributes. That is because in our testing we generally apply `#[no_mangle]` to functions that are tested. I've added a test now that deliberately has no attributes
2025-06-23rustdoc-json: Add test for `#[optimize(..)]`Alona Enraght-Moony-0/+13
Follow up to https://www.github.com/rust-lang/rust/pull/138291
2025-06-23tests: Add `RUST_BACKTRACE` and `-Cpanic` revisions to `panic-main.rs` testMartin Nordholts-0/+23
2025-06-23tests: Bless cannot-be-called and dedup with unsupported ABI testJubilee Young-1147/+414
2025-06-23tests: Verify varargs with unsupported fn ptr ABIs must errorJubilee Young-0/+27
2025-06-23tests: Adopt ABI transmute tests from crashtestsJubilee Young-7/+31
2025-06-23tests: Update and bless cmse-nonsecure ABI testsJubilee Young-32/+29
2025-06-23tests: Update raw-dylib unsupported ABI testJubilee Young-2/+2
2025-06-23tests: Enhance unsupported ABI testsJubilee Young-1856/+1096
We have fairly different error messages now and handle more cases, so we augment the test in tests/ui/abi/unsupported.rs with more examples to handle structs, traits, and impls on same when those feature the unsupported ABIs of interest.
2025-06-23tests: Bless abi_gpu_kernel feature gate testJubilee Young-66/+57
2025-06-23Improve code and documentationGuillaume Gomez-3/+31
2025-06-23Add ui test for `redundant_explicit_links` rustdoc lint for items coming ↵Guillaume Gomez-0/+51
from expansion
2025-06-23cleaned up some testsKivooeo-148/+151
2025-06-23mbe: Restructure `macro_metavar_expr` testsTrevor Gross-55/+57
These tests have expanded beyond the RFC, so rename the directory `rfc-3086-metavar-expr` to `metavar-expressions`. `concat` (which wasn't part of the RFC) now fits in this group, so merge its tests into the `metavar-expressions` directory. Additionally rename some related `issue-*` tests.
2025-06-23Rollup merge of #142892 - jdonszelmann:fix-142891, r=oli-obkJana Dönszelmann-0/+19
Fix ICE on debug builds where lints are delayed on the crate root r? ``@oli-obk`` Closes rust-lang/rust#142891 thanks to ``@JonathanBrouwer`` for finding it!
2025-06-23Rollup merge of #142822 - oli-obk:const-partial-eq, r=fee1-deadJana Dönszelmann-597/+101
Make `PartialEq` a `const_trait` r? ``@fee1-dead`` or ``@compiler-errors`` something generally useful but also required for https://github.com/rust-lang/rust/pull/142789
2025-06-23move naked checks out of check_attr.rsJana Dönszelmann-22/+22
2025-06-23fix 142891Jana Dönszelmann-0/+16
2025-06-23test for lint on root node crashJana Dönszelmann-0/+3
2025-06-23Make `PartialEq` a `const_trait`Oli Scherer-597/+101
2025-06-23Rollup merge of #142823 - JonathanBrouwer:no_mangle_parser, r=jdonszelmannMatthias Krüger-12/+12
Port `#[no_mangle]` to new attribute parsing infrastructure Ports `no_mangle` to the new attribute parsing infrastructure for https://github.com/rust-lang/rust/issues/131229#issuecomment-2971353197 r? ``@jdonszelmann``
2025-06-23Rollup merge of #141597 - Oneirical:unquestionable-instruction, r=jieyouxuMatthias Krüger-0/+1594
Document subdirectories of UI tests with README files Part of rust-lang/rust#133895 and the [2025 Google Summer of Code](https://blog.rust-lang.org/2025/05/08/gsoc-2025-selected-projects/) associated project. When adding a new UI test, one is faced with hundreds of subdirectories in `tests/ui` reflecting various categories. Knowing where to put the new test is not trivial, as many of the categories have slightly misleading names. For example, `moves` does not only refer to the `move` keyword but to functions taking ownership in general, whereas `allocator` does not refer to allocation in general but rather to the very specific `allocator_api` and `global_allocator` features. Many contributors will therefore place their test at the top level of ̀`tests/ui` where it will be mixed with hundreds of unrelated tests. This PR is a tentative move towards more clearly defined tag/categories, with a SUMMARY.md file documenting the true purpose of each subdirectory, placed inside `tests/ui`. r? ``@jieyouxu``
2025-06-22Stop collecting unmentioned constantsMark Rousskov-5/+0
This avoids generating useless dead LLVM IR.
2025-06-22Only inherit local hash for paths.Camille GILLOT-9/+9
2025-06-22Port `#[no_mangle]` to new attribute parsing infrastructureJonathan Brouwer-12/+12
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
2025-06-22Auto merge of #142508 - Mark-Simulacrum:skip-noop-drop-glue, r=fee1-deadbors-16/+76
Skip no-op drop glue Since rust-lang/rust#122662 this no longer gets used in vtables, so we're safe to fully drop generating functions from vtables. Those are eventually cleaned up by LLVM, but it's wasteful to produce them in the first place. This doesn't appear to be a significant win (and shows some slight regressions) but seems like the right thing to do. At minimum it reduces noise in the LLVM IR we generate, which seems like a good thing.
2025-06-22add method to retrieve body of coroutineMakai-0/+105
2025-06-22Auto merge of #142878 - GuillaumeGomez:rollup-53dohob, r=GuillaumeGomezbors-350/+325
Rollup of 10 pull requests Successful merges: - rust-lang/rust#142458 (Merge unboxed trait object error suggestion into regular dyn incompat error) - rust-lang/rust#142593 (Add a warning to LateContext::get_def_path) - rust-lang/rust#142594 (Add DesugaringKind::FormatLiteral) - rust-lang/rust#142740 (Clean-up `FnCtxt::is_destruct_assignment_desugaring`) - rust-lang/rust#142780 (Port `#[must_use]` to new attribute parsing infrastructure) - rust-lang/rust#142798 (Don't fail to parse a struct if a semicolon is used to separate fields) - rust-lang/rust#142856 (Add a few inline directives in rustc_serialize.) - rust-lang/rust#142868 (remove few allow(dead_code)) - rust-lang/rust#142874 (cranelift: fix target feature name typo: "fxsr") - rust-lang/rust#142877 (Document why tidy checks if `eslint` is installed via `npm`) r? `@ghost` `@rustbot` modify labels: rollup
2025-06-22Add a SUMMARY.md outlining immediate subdirectories of the ui test suiteOneirical-0/+1594
Co-authored-by: Jieyou Xu <jieyouxu@outlook.com>
2025-06-22Fix tests to drop now-skipped codegenMark Rousskov-16/+53
2025-06-22Rollup merge of #142798 - camsteffen:recover-semi, r=compiler-errorsGuillaume Gomez-9/+9
Don't fail to parse a struct if a semicolon is used to separate fields The first commit is a small refactor.
2025-06-22Rollup merge of #142780 - JonathanBrouwer:must_use_new_attr, r=jdonszelmannGuillaume Gomez-40/+36
Port `#[must_use]` to new attribute parsing infrastructure Ports `must_use` to the new attribute parsing infrastructure for https://github.com/rust-lang/rust/issues/131229#issuecomment-2971353197 r? `@jdonszelmann`
2025-06-22Rollup merge of #142594 - mejrs:new_desugaring, r=chenyukangGuillaume Gomez-148/+211
Add DesugaringKind::FormatLiteral Implements `DesugaringKind::FormatLiteral` to mark the FormatArgs desugaring of format literals. The main use for this is to stop yapping about about formatting parameters if we're not anywhere near a format literal. The other use case is to fix suggestions such as https://github.com/rust-lang/rust/issues/141350. It might also be useful for new or existing diagnostics that check whether they're in a format-like macro. cc `@xizheyin` `@fmease`
2025-06-22Rollup merge of #142458 - oli-obk:dyn-incompat, r=compiler-errorsGuillaume Gomez-153/+69
Merge unboxed trait object error suggestion into regular dyn incompat error Another hir-walker removed from the well-formed queries. This error was always a duplicate of another, but it was able to provide more information because it could invoke `is_dyn_compatible` without worrying about cycle errors. That's also the reason we can't put the error directly into hir_ty_lowering when lowering a `dyn Trait` within an associated item signature. So instead I packed it into the error handling of wf obligation checking.
2025-06-22Don't suggest changing a method inside a expansionUrgau-2/+32
2025-06-22Address review commentsUrgau-2/+12
2025-06-22Auto merge of #142706 - fee1-dead-contrib:push-zsznlqyrzsqo, r=oli-obkbors-2/+4
completely deduplicate `Visitor` and `MutVisitor` r? oli-obk This closes rust-lang/rust#127615. ### Discussion > * Give every `MutVisitor::visit_*` method a corresponding `flat_map_*` method. Not every AST node exists in a location where they can be mapped to multiple instances of themselves. Not every AST node exists in a location where they can be removed from existence (e.g. `filter_map_expr`). I don't think this is doable. > * Give every `MutVisitor::visit_*` method a corresponding `Visitor` method and vice versa The only three remaining method-level asymmetries after this PR are `visit_stmt` and `visit_nested_use_tree` (only on `Visitor`) and `visit_span` (only on `MutVisitor`). `visit_stmt` doesn't seem applicable to `MutVisitor` because `walk_flat_map_stmt_kind` will ask `flat_map_item` / `filter_map_expr` to potentially turn a single `Stmt` to multiple based on what a visitor wants. So only using `flat_map_stmt` seems appropriate. `visit_nested_use_tree` is used for `rustc_resolve` to track stuff. Not useful for `MutVisitor` for now. `visit_span` is currently not used for `MutVisitor` already, it was just kept in case we want to revive rust-lang/rust#127241. cc `@cjgillot` maybe we could remove for now and re-insert later if we find a use-case? It does involve some extra effort to maintain. * Remaining FIXMEs `visit_lifetime` has an extra param for `Visitor` that's not in `MutVisitor`. This is again something only used by `rustc_resolve`. I think we can keep that symmetry for now.
2025-06-22Port `#[must_use]` to new attribute parsing infrastructureJonathan Brouwer-40/+36
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
2025-06-22Stop dbg! macro yapping about format modifiersmejrs-9/+25
2025-06-22Implement DesugaringKind::FormatLiteralmejrs-143/+190
2025-06-22Rollup merge of #142850 - tshepang:patch-1, r=jieyouxuJacob Pratt-1/+0
remove asm_goto feature annotation, for it is now stabilized This was stabilized in https://github.com/rust-lang/rust/pull/133870
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-11 06:37:26 +0000