<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/ui/codemap_tests, branch master</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=master</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-09-19T18:28:44+00:00</updated>
<entry>
<title>chore(compiletest): Use newest anstyle-svg version</title>
<updated>2025-09-19T18:28:44+00:00</updated>
<author>
<name>Scott Schafer</name>
<email>schaferjscott@gmail.com</email>
</author>
<published>2025-09-16T07:48:24+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=82eed00d3979b74315f66201c6bf4d3f00d38c25'/>
<id>urn:sha1:82eed00d3979b74315f66201c6bf4d3f00d38c25</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "Rollup merge of #122661 - estebank:assert-macro-span, r=petrochenkov"</title>
<updated>2025-09-11T01:10:46+00:00</updated>
<author>
<name>Jieyou Xu</name>
<email>jieyouxu@outlook.com</email>
</author>
<published>2025-09-11T01:00:01+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b38a86f4d7c28ae9ab153b87c7e45037e56306fb'/>
<id>urn:sha1:b38a86f4d7c28ae9ab153b87c7e45037e56306fb</id>
<content type='text'>
This reverts commit 1eeb8e8b151d1da7daa73837a25dc5f7a1a7fa28, reversing
changes made to 324bf2b9fd8bf9661e7045c8a93f5ff0ec1a8ca5.

Unfortunately the assert desugaring change is not backwards compatible,
see RUST-145770.

Code such as

```rust
#[derive(Debug)]
struct F {
    data: bool
}

impl std::ops::Not for F {
  type Output = bool;
  fn not(self) -&gt; Self::Output { !self.data }
}

fn main() {
  let f = F { data: true };

  assert!(f);
}
```

would be broken by the assert desugaring change. We may need to land
the change over an edition boundary, or limit the editions that the
desugaring change impacts.
</content>
</entry>
<entry>
<title>Change the desugaring of `assert!` for better error output</title>
<updated>2025-08-12T16:30:48+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2024-03-17T20:46:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c439a59dbd275aef9bc24c7172e2111ccc3794c3'/>
<id>urn:sha1:c439a59dbd275aef9bc24c7172e2111ccc3794c3</id>
<content type='text'>
In the desugaring of `assert!`, we now expand to a `match` expression
instead of `if !cond {..}`.

The span of incorrect conditions will point only at the expression, and not
the whole `assert!` invocation.

```
error[E0308]: mismatched types
  --&gt; $DIR/issue-14091.rs:2:13
   |
LL |     assert!(1,1);
   |             ^ expected `bool`, found integer
```

We no longer mention the expression needing to implement the `Not` trait.

```
error[E0308]: mismatched types
  --&gt; $DIR/issue-14091-2.rs:15:13
   |
LL |     assert!(x, x);
   |             ^ expected `bool`, found `BytePos`
```

`assert!(val)` now desugars to:

```rust
match val {
    true =&gt; {},
    _ =&gt; $crate::panic::panic_2021!(),
}
```

Fix #122159.

We make some minor changes to some diagnostics to avoid span overlap on
type mismatch or inverted "expected"/"found" on type errors.

We remove some unnecessary parens from core, alloc and miri.

address review comments
</content>
</entry>
<entry>
<title>expand: Micro-optimize prelude injection</title>
<updated>2025-07-28T14:35:09+00:00</updated>
<author>
<name>Vadim Petrochenkov</name>
<email>vadim.petrochenkov@gmail.com</email>
</author>
<published>2025-07-28T14:24:28+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c56f49dc34f43568122f057d72f3472b3fcd4d8e'/>
<id>urn:sha1:c56f49dc34f43568122f057d72f3472b3fcd4d8e</id>
<content type='text'>
Use `splice` to avoid shifting the other items twice.
Put `extern crate std;` first so it's already resolved when we resolve `::std::prelude::rust_20XX`.

</content>
</entry>
<entry>
<title>Move more tests/ui tests</title>
<updated>2025-05-12T14:35:09+00:00</updated>
<author>
<name>mejrs</name>
<email>59372212+mejrs@users.noreply.github.com</email>
</author>
<published>2025-05-12T14:35:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=60c32f61aeb5a22c1bd956b64fb9dfc24dd94fe5'/>
<id>urn:sha1:60c32f61aeb5a22c1bd956b64fb9dfc24dd94fe5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #139967 - jieyouxu:auxiliary, r=wesleywiser</title>
<updated>2025-04-17T19:53:25+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-04-17T19:53:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=026d56b0f6e2340b1363f3db1bc44f7cedbf7a72'/>
<id>urn:sha1:026d56b0f6e2340b1363f3db1bc44f7cedbf7a72</id>
<content type='text'>
Introduce and use specialized `//@ ignore-auxiliary` for test support files instead of using `//@ ignore-test`

### Summary

Add a semantically meaningful directive for ignoring test *auxiliary* files. This is for auxiliary files that *participate* in actual tests but should not be built by `compiletest` (i.e. these files are involved through `mod xxx;` or `include!()` or `#[path = "xxx"]`, etc.).

### Motivation

A specialized directive like `//@ ignore-auxiliary` makes it way easier to audit disabled tests via `//@ ignore-test`.
  - These support files cannot use the canonical `auxiliary/` dir because they participate in module resolution or are included, or their relative paths can be important for test intention otherwise.

Follow-up to:
- #139705
- #139783
- #139740

See also discussions in:

- [#t-compiler &gt; Directive name for non-test aux files?](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Directive.20name.20for.20non-test.20aux.20files.3F/with/512773817)
- [#t-compiler &gt; Handling disabled &amp;#96;//@ ignore-test&amp;#96; tests](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Handling.20disabled.20.60.2F.2F.40.20ignore-test.60.20tests/with/512005974)
- [#t-compiler/meetings &gt; &amp;#91;steering&amp;#93; 2025-04-11 Dealing with disabled tests](https://rust-lang.zulipchat.com/#narrow/channel/238009-t-compiler.2Fmeetings/topic/.5Bsteering.5D.202025-04-11.20Dealing.20with.20disabled.20tests/with/511717981)

### Remarks on remaining unconditionally disabled tests under `tests/`

After this PR, against commit 79a272c6402, only **14** remaining test files are disabled through `//@ ignore-test`:

&lt;details&gt;
&lt;summary&gt;Remaining `//@ ignore-test` files under `tests/`&lt;/summary&gt;

```
tests/debuginfo/drop-locations.rs
4://@ ignore-test (broken, see #128971)

tests/rustdoc/macro-document-private-duplicate.rs
1://@ ignore-test (fails spuriously, see issue #89228)

tests/rustdoc/inline_cross/assoc-const-equality.rs
3://@ ignore-test (FIXME: #125092)

tests/ui/match/issue-27021.rs
7://@ ignore-test (#54987)

tests/ui/match/issue-26996.rs
7://@ ignore-test (#54987)

tests/ui/issues/issue-49298.rs
9://@ ignore-test (#54987)

tests/ui/issues/issue-59756.rs
2://@ ignore-test (rustfix needs multiple suggestions)

tests/ui/precondition-checks/write.rs
5://@ ignore-test (unimplemented)

tests/ui/precondition-checks/read.rs
5://@ ignore-test (unimplemented)

tests/ui/precondition-checks/write_bytes.rs
5://@ ignore-test (unimplemented)

tests/ui/explicit-tail-calls/drop-order.rs
2://@ ignore-test: tail calls are not implemented in rustc_codegen_ssa yet, so this causes 🧊

tests/ui/panics/panic-short-backtrace-windows-x86_64.rs
3://@ ignore-test (#92000)

tests/ui/json/json-bom-plus-crlf-multifile-aux.rs
3://@ ignore-test Not a test. Used by other tests

tests/ui/traits/next-solver/object-soundness-requires-generalization.rs
2://@ ignore-test (see #114196)
```
&lt;/details&gt;

Of these, most are either **unimplemented**, or **spurious**, or **known-broken**. The outstanding one is `tests/ui/json/json-bom-plus-crlf-multifile-aux.rs` which I did not want to touch in *this* PR -- that aux file has load-bearing BOM and carriage returns and byte offset matters. I think those test files that require special encoding / BOM probably are better off as `run-make` tests. See #139968 for that aux file.

### Review advice

- Best reviewed commit-by-commit.
- The directive name diverged from the most voted `//@ auxiliary` because I think that's easy to confuse with `//@ aux-{crate,dir}`.

r? compiler
</content>
</entry>
<entry>
<title>tests: use `//@ ignore-auxiliary` with backlinked primary test file</title>
<updated>2025-04-17T11:45:28+00:00</updated>
<author>
<name>Jieyou Xu</name>
<email>jieyouxu@outlook.com</email>
</author>
<published>2025-04-17T09:22:56+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=89cac55bb85e91ad4d90f9e0bcf0c0e065b88a7d'/>
<id>urn:sha1:89cac55bb85e91ad4d90f9e0bcf0c0e065b88a7d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Explicitly annotate edition for `unpretty=expanded` and `unpretty=hir` tests</title>
<updated>2025-04-16T09:10:10+00:00</updated>
<author>
<name>Lukas Wirth</name>
<email>lukas.wirth@ferrous-systems.com</email>
</author>
<published>2025-04-16T08:45:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=20ab952b4dd994aa6e22ff56df5314eee5ff415c'/>
<id>urn:sha1:20ab952b4dd994aa6e22ff56df5314eee5ff415c</id>
<content type='text'>
These emit prelude imports which means they are always edition dependent
</content>
</entry>
<entry>
<title>Remove attribute `#[rustc_error]`</title>
<updated>2025-03-29T22:32:21+00:00</updated>
<author>
<name>Vadim Petrochenkov</name>
<email>vadim.petrochenkov@gmail.com</email>
</author>
<published>2025-03-29T21:39:55+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2dfd2a2a242e920b7378328b87f901652d9d81be'/>
<id>urn:sha1:2dfd2a2a242e920b7378328b87f901652d9d81be</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not suggest using `-Zmacro-backtrace` for builtin macros</title>
<updated>2025-03-14T19:50:03+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2025-03-11T23:42:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f0b8e13b59a68d63cf7083be5cd6dcca3abf18ff'/>
<id>urn:sha1:f0b8e13b59a68d63cf7083be5cd6dcca3abf18ff</id>
<content type='text'>
For macros that are implemented on the compiler, we do *not* mention the `-Zmacro-backtrace` flag. This includes `derive`s and standard macros.
</content>
</entry>
</feed>
