Skip to content

Commit 56c4dcd

Browse files
committed
Auto merge of #153315 - JonathanBrouwer:rollup-Nob61Uk, r=JonathanBrouwer
Rollup of 8 pull requests Successful merges: - #151864 (Implement AST -> HIR generics propagation in delegation) - #152941 (prefer actual ABI-controling fields over target.abi when making ABI decisions) - #153227 (Don’t report missing fields in struct exprs with syntax errors.) - #152966 (Migrate 11 tests from tests/ui/issues to specific directories) - #153003 (rustdoc: make `--emit` and `--out-dir` mimic rustc) - #153034 (Remove unhelpful hint from trivial bound errors) - #153221 (Add release notes for 1.94.0) - #153297 (Update the name of the Hermit operating system)
2 parents ec818fd + 3e29ac3 commit 56c4dcd

124 files changed

Lines changed: 2361 additions & 4033 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

RELEASES.md

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,118 @@
1+
Version 1.94.0 (2026-03-05)
2+
==========================
3+
4+
<a id="1.94.0-Language"></a>
5+
6+
Language
7+
--------
8+
- [Impls and impl items inherit `dead_code` lint level of the corresponding traits and trait items](https://github.com/rust-lang/rust/pull/144113)
9+
- [Stabilize additional 29 RISC-V target features including large portions of the RVA22U64 / RVA23U64 profiles](https://github.com/rust-lang/rust/pull/145948)
10+
- [Add warn-by-default `unused_visibilities` lint for visibility on `const _` declarations](https://github.com/rust-lang/rust/pull/147136)
11+
- [Update to Unicode 17](https://github.com/rust-lang/rust/pull/148321)
12+
- [Avoid incorrect lifetime errors for closures](https://github.com/rust-lang/rust/pull/148329)
13+
14+
<a id="1.94.0-Platform-Support"></a>
15+
16+
Platform Support
17+
----------------
18+
19+
- [Add `riscv64im-unknown-none-elf` as a tier 3 target](https://github.com/rust-lang/rust/pull/148790)
20+
21+
Refer to Rust's [platform support page][platform-support-doc]
22+
for more information on Rust's tiered platform support.
23+
24+
[platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html
25+
26+
<a id="1.94.0-Libraries"></a>
27+
28+
Libraries
29+
---------
30+
31+
- [Relax `T: Ord` bound for some `BinaryHeap<T>` methods.](https://github.com/rust-lang/rust/pull/149408)
32+
33+
<a id="1.94.0-Stabilized-APIs"></a>
34+
35+
Stabilized APIs
36+
---------------
37+
38+
- [`<[T]>::array_windows`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.array_windows)
39+
- [`<[T]>::element_offset`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.element_offset)
40+
- [`LazyCell::get`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get)
41+
- [`LazyCell::get_mut`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.get_mut)
42+
- [`LazyCell::force_mut`](https://doc.rust-lang.org/stable/std/cell/struct.LazyCell.html#method.force_mut)
43+
- [`LazyLock::get`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get)
44+
- [`LazyLock::get_mut`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.get_mut)
45+
- [`LazyLock::force_mut`](https://doc.rust-lang.org/stable/std/sync/struct.LazyLock.html#method.force_mut)
46+
- [`impl TryFrom<char> for usize`](https://doc.rust-lang.org/stable/std/convert/trait.TryFrom.html#impl-TryFrom%3Cchar%3E-for-usize)
47+
- [`std::iter::Peekable::next_if_map`](https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map)
48+
- [`std::iter::Peekable::next_if_map_mut`](https://doc.rust-lang.org/stable/std/iter/struct.Peekable.html#method.next_if_map_mut)
49+
- [x86 `avx512fp16` intrinsics](https://github.com/rust-lang/rust/issues/127213)
50+
(excluding those that depend directly on the unstable `f16` type)
51+
- [AArch64 NEON fp16 intrinsics](https://github.com/rust-lang/rust/issues/136306)
52+
(excluding those that depend directly on the unstable `f16` type)
53+
- [`f32::consts::EULER_GAMMA`](https://doc.rust-lang.org/stable/std/f32/consts/constant.EULER_GAMMA.html)
54+
- [`f64::consts::EULER_GAMMA`](https://doc.rust-lang.org/stable/std/f64/consts/constant.EULER_GAMMA.html)
55+
- [`f32::consts::GOLDEN_RATIO`](https://doc.rust-lang.org/stable/std/f32/consts/constant.GOLDEN_RATIO.html)
56+
- [`f64::consts::GOLDEN_RATIO`](https://doc.rust-lang.org/stable/std/f64/consts/constant.GOLDEN_RATIO.html)
57+
58+
59+
These previously stable APIs are now stable in const contexts:
60+
61+
- [`f32::mul_add`](https://doc.rust-lang.org/stable/std/primitive.f32.html#method.mul_add)
62+
- [`f64::mul_add`](https://doc.rust-lang.org/stable/std/primitive.f64.html#method.mul_add)
63+
64+
65+
<a id="1.94.0-Cargo"></a>
66+
67+
Cargo
68+
-----
69+
70+
- Stabilize the config include key. The top-level include config key allows loading additional config files, enabling better organization, sharing, and management of Cargo configurations across projects and environments. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#including-extra-configuration-files) [#16284](https://github.com/rust-lang/cargo/pull/16284)
71+
- Stabilize the pubtime field in registry index. This records when a crate version was published and enables time-based dependency resolution in the future. Note that crates.io will gradually backfill existing packages when a new version is published. Not all crates have pubtime yet. [#16369](https://github.com/rust-lang/cargo/pull/16369) [#16372](https://github.com/rust-lang/cargo/pull/16372)
72+
- Cargo now parses [TOML v1.1](https://toml.io/en/v1.1.0) for manifests and configuration files. Note that using these features in Cargo.toml will raise your development MSRV, but the published manifest remains compatible with older parsers. [#16415](https://github.com/rust-lang/cargo/pull/16415)
73+
- [Make `CARGO_BIN_EXE_<crate>` available at runtime ](https://github.com/rust-lang/cargo/pull/16421/)
74+
75+
<a id="1.94.0-Compatibility-Notes"></a>
76+
77+
Compatibility Notes
78+
-------------------
79+
- [Forbid freely casting lifetime bounds of `dyn`-types](https://github.com/rust-lang/rust/pull/136776)
80+
- [Make closure capturing have consistent and correct behaviour around patterns](https://github.com/rust-lang/rust/pull/138961)
81+
Some finer details of how precise closure captures get affected by pattern matching have been changed. In some cases, this can cause a non-move closure that was previously capturing an entire variable by move, to now capture only part of that variable by move, and other parts by borrow. This can cause the borrow checker to complain where it previously didn't, or cause `Drop` to run at a different point in time.
82+
- [Standard library macros are now imported via prelude, not via injected `#[macro_use]`](https://github.com/rust-lang/rust/pull/139493)
83+
This will raise an error if macros of the same name are glob imported.
84+
For example if a crate defines their own `matches` macro and then glob imports that,
85+
it's now ambiguous whether the custom or standard library `matches` is meant and
86+
an explicit import of the name is required to resolve the ambiguity.
87+
One exception is `core::panic` and `std::panic`, if their import is ambiguous
88+
a new warning ([`ambiguous_panic_imports`](https://github.com/rust-lang/rust/issues/147319)) is raised.
89+
This may raise a new warning ([`ambiguous_panic_imports`](https://github.com/rust-lang/rust/issues/147319)) on `#![no_std]` code glob importing the std crate.
90+
Both `core::panic!` and `std::panic!` are then in scope and which is used is ambiguous.
91+
- [Don't strip shebang in expression-context `include!(…)`s](https://github.com/rust-lang/rust/pull/146377)
92+
This can cause previously working includes to no longer compile if they included files which started with a shebang.
93+
- [Ambiguous glob reexports are now also visible cross-crate](https://github.com/rust-lang/rust/pull/147984)
94+
This unifies behavior between local and cross-crate errors on these exports, which may introduce new ambiguity errors.
95+
- [Don't normalize where-clauses before checking well-formedness](https://github.com/rust-lang/rust/pull/148477)
96+
- [Introduce a future compatibility warning on codegen attributes on body-free trait methods](https://github.com/rust-lang/rust/pull/148756)
97+
These attributes currently have no effect in this position.
98+
- [On Windows `std::time::SystemTime::checked_sub_duration` will return `None` for times before the Windows epoch (1/1/1601)](https://github.com/rust-lang/rust/pull/148825)
99+
- [Lifetime identifiers such as `'a` are now NFC normalized](https://github.com/rust-lang/rust/pull/149192).
100+
- [Overhaul filename handling for cross-compiler consistency](https://github.com/rust-lang/rust/pull/149709)
101+
Any paths emitted by compiler now always respect the relative-ness of the paths and `--remap-path-prefix` given originally.
102+
One side-effect of this change is that paths emitted for local crates in Cargo (path dependencies and workspace members) are no longer absolute but relative when emitted as part of a diagnostic in a downstream crate.
103+
104+
<a id="1.94.0-Internal-Changes"></a>
105+
106+
Internal Changes
107+
----------------
108+
109+
These changes do not affect any public interfaces of Rust, but they represent
110+
significant improvements to the performance or internals of rustc and related
111+
tools.
112+
113+
- [Switch to `annotate-snippets` for error emission](https://github.com/rust-lang/rust/pull/150032)
114+
This should preserve mostly the same outputs in rustc error messages.
115+
1116
Version 1.93.1 (2026-02-12)
2117
===========================
3118

compiler/rustc_ast/src/ast.rs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1724,6 +1724,12 @@ pub enum StructRest {
17241724
Rest(Span),
17251725
/// No trailing `..` or expression.
17261726
None,
1727+
/// No trailing `..` or expression, and also, a parse error occurred inside the struct braces.
1728+
///
1729+
/// This struct should be treated similarly to as if it had an `..` in it,
1730+
/// in particular rather than reporting missing fields, because the parse error
1731+
/// makes which fields the struct was intended to have not fully known.
1732+
NoneWithError(ErrorGuaranteed),
17271733
}
17281734

17291735
#[derive(Clone, Encodable, Decodable, Debug, Walkable)]

0 commit comments

Comments
 (0)