<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/ui-fulldeps/session-diagnostic/subdiagnostic-derive.rs, 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>2024-07-24T21:03:27+00:00</updated>
<entry>
<title>Do not use question as label</title>
<updated>2024-07-24T21:03:27+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2024-07-23T19:43:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=850faea030db4b260719d99be4191d7803efdb35'/>
<id>urn:sha1:850faea030db4b260719d99be4191d7803efdb35</id>
<content type='text'>
We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might":

```
error[E0432]: unresolved import `spam`
  --&gt; $DIR/import-from-missing-star-3.rs:2:9
   |
LL |     use spam::*;
   |         ^^^^ you might be missing crate `spam`
   |
   = help: consider adding `extern crate spam` to use the `spam` crate
```
</content>
</entry>
<entry>
<title>Allow nesting subdiagnostics</title>
<updated>2024-04-21T07:45:03+00:00</updated>
<author>
<name>Xiretza</name>
<email>xiretza@xiretza.xyz</email>
</author>
<published>2024-04-20T12:52:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c88bb6c011a034a8b29d2a61734de0d36a02a1e9'/>
<id>urn:sha1:c88bb6c011a034a8b29d2a61734de0d36a02a1e9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename `SubdiagnosticMessage` as `SubdiagMessage`.</title>
<updated>2024-03-05T01:14:49+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2024-02-29T03:53:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=60ea6e2831952110b81fd76190ee66a2f094febd'/>
<id>urn:sha1:60ea6e2831952110b81fd76190ee66a2f094febd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename `DiagnosticMessage` as `DiagMessage`.</title>
<updated>2024-03-05T01:14:49+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2024-02-29T00:58:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=18715c98c67235274843974c928a70e84946398b'/>
<id>urn:sha1:18715c98c67235274843974c928a70e84946398b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives</title>
<updated>2024-02-22T16:04:04+00:00</updated>
<author>
<name>许杰友 Jieyou Xu (Joe)</name>
<email>jieyouxu@outlook.com</email>
</author>
<published>2024-02-22T12:10:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6e48b96692d63a79a14563f27fe5185f122434f8'/>
<id>urn:sha1:6e48b96692d63a79a14563f27fe5185f122434f8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use `rustc_fluent_macro::fluent_messages!` directly.</title>
<updated>2023-11-25T21:38:40+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2023-11-21T22:53:07+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=57cd5e6551ffcd071aa0496f9b8c0ed28dca7ffe'/>
<id>urn:sha1:57cd5e6551ffcd071aa0496f9b8c0ed28dca7ffe</id>
<content type='text'>
Currently we always do this:
```
use rustc_fluent_macro::fluent_messages;
...
fluent_messages! { "./example.ftl" }
```
But there is no need, we can just do this everywhere:
```
rustc_fluent_macro::fluent_messages! { "./example.ftl" }
```
which is shorter.
</content>
</entry>
<entry>
<title>Bump syn dependency</title>
<updated>2023-07-26T08:42:40+00:00</updated>
<author>
<name>Oli Scherer</name>
<email>git-spam-no-reply9815368754983@oli-obk.de</email>
</author>
<published>2023-07-26T08:42:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=ad8303739f9f62827e2192eb991b951809369a54'/>
<id>urn:sha1:ad8303739f9f62827e2192eb991b951809369a54</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use translatable diagnostics in `rustc_const_eval`</title>
<updated>2023-06-01T14:45:18+00:00</updated>
<author>
<name>Deadbeef</name>
<email>ent3rm4n@gmail.com</email>
</author>
<published>2023-05-17T10:30:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4f83717cf768adb0b0dfe23b8eecf2b259eec354'/>
<id>urn:sha1:4f83717cf768adb0b0dfe23b8eecf2b259eec354</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add `rustc_fluent_macro` to decouple fluent from `rustc_macros`</title>
<updated>2023-04-18T18:56:22+00:00</updated>
<author>
<name>Nilstrieb</name>
<email>48135649+Nilstrieb@users.noreply.github.com</email>
</author>
<published>2023-04-16T12:33:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b5d3d970fa64c25eecfbd8ebbae601a2c6cb2cb3'/>
<id>urn:sha1:b5d3d970fa64c25eecfbd8ebbae601a2c6cb2cb3</id>
<content type='text'>
Fluent, with all the icu4x it brings in, takes quite some time to
compile. `fluent_messages!` is only needed in further downstream rustc
crates, but is blocking more upstream crates like `rustc_index`. By
splitting it out, we allow `rustc_macros` to be compiled earlier, which
speeds up `x check compiler` by about 5 seconds (and even more after the
needless dependency on `serde_json` is removed from
`rustc_data_structures`).
</content>
</entry>
<entry>
<title>Support `x test --stage 1 ui-fulldeps`</title>
<updated>2023-04-18T03:40:31+00:00</updated>
<author>
<name>jyn</name>
<email>github@jyn.dev</email>
</author>
<published>2023-04-18T01:00:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=d6af60266eed9a19ee550278cdfe1d2857763286'/>
<id>urn:sha1:d6af60266eed9a19ee550278cdfe1d2857763286</id>
<content type='text'>
Nils had an excellent idea the other day: the same way that rustdoc is
able to load `rustc_driver` from the sysroot, ui-fulldeps tests should
also be able to load it from the sysroot. That allows us to run fulldeps
tests with stage1, without having to fully rebuild the compiler twice.
It does unfortunately have the downside that we're running the tests on
the *bootstrap* compiler, not the in-tree sources, but since most of the
fulldeps tests are for the *API* of the compiler, that seems ok.

I think it's possible to extend this to `run-make-fulldeps`, but I've
run out of energy for tonight.

- Move `plugin` tests into a subdirectory.

  Plugins are loaded at runtime with `dlopen` and so require the ABI of
  the running compile to match the ABI of the compiler linked with
  `rustc_driver`. As a result they can't be supported in stage 1 and have
  to use `// ignore-stage1`.

- Remove `ignore-stage1` from most non-plugin tests

- Ignore diagnostic tests in stage 1. Even though this requires a stage
  2 build to load rustc_driver, it's primarily testing the error message
  that the *running* compiler emits when the diagnostic struct is malformed.

- Pass `-Zforce-unstable-if-unmarked` in stage1, not just stage2. That
  allows running `hash-stable-is-unstable` in stage1, since it now
  suggests adding `rustc_private` to enable loading the crates.

- Add libLLVM.so to the stage0 target sysroot, to allow fulldeps tests
  that act as custom drivers to load it at runtime.

- Pass `--sysroot stage0-sysroot` in compiletest so that we use the
  correct version of std.
</content>
</entry>
</feed>
