rust/compiler/rustc_feature/src/unstable.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-13T15:55:06+00:00update issue number for `const_trait_impl`2025-07-13T15:55:06+00:00Deadbeefent3rm4n@gmail.com2025-07-13T08:21:25+00:00urn:sha1:6b02597ed3dc7a7c3581960ca6afae575f6c691eAuto merge of #143214 - camsteffen:remove-let-chains-feature, r=est312025-07-02T17:18:47+00:00borsbors@rust-lang.org2025-07-02T17:18:47+00:00urn:sha1:1ce9c977ffcff7c3b12bfe5629a682da0e74a7a1
Remove let_chains unstable feature
Per https://github.com/rust-lang/rust/issues/53667#issuecomment-3016742982 (but then I also noticed rust-lang/rust#140722)
This replaces the feature gate with a parser error that says let chains require 2024.
A lot of tests were using the unstable feature. I either added edition:2024 to the test or split out the parts that require 2024.
Auto merge of #142974 - cuviper:stage0-bump, r=Mark-Simulacrum2025-07-02T01:41:18+00:00borsbors@rust-lang.org2025-07-02T01:41:18+00:00urn:sha1:f51c9870bab634afb9e7a262b6ca7816bb9e940d
Update stage0 to 1.89.0-beta.1
- Update version placeholders
- Update stage0 to 1.89.0-beta.1
- Update `STAGE0_MISSING_TARGETS`
- Update `cfg(bootstrap)`
r? `@Mark-Simulacrum`
try-job: dist-i586-gnu-i586-i686-musl
Remove support for dyn*2025-07-01T19:00:21+00:00Michael Gouletmichael@errs.io2025-06-26T02:01:38+00:00urn:sha1:2516c339829cd9193c15464218a981b8547157caUpdate version placeholders2025-07-01T17:54:33+00:00Josh Stonejistone@redhat.com2025-06-23T17:24:40+00:00urn:sha1:9ce8930da62a9be15831b78b9834d91702872e15Remove let_chains feature2025-06-30T12:49:20+00:00Cameron Steffencam.steffen94@gmail.com2025-06-29T18:06:21+00:00urn:sha1:dc9879cb3d3446c41b6d7d6813b7bfd17da1134fRollup merge of #139858 - oli-obk:new-const-traits-syntax, r=fee1-dead2025-06-27T20:13:00+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-06-27T20:13:00+00:00urn:sha1:36c2b011cb4bb9bd34647486551e85a969773c8d
New const traits syntax
This PR only affects the AST and doesn't actually change anything semantically.
All occurrences of `~const` outside of libcore have been replaced by `[const]`. Within libcore we have to wait for rustfmt to be bumped in the bootstrap compiler. This will happen "automatically" (when rustfmt is run) during the bootstrap bump, as rustfmt converts `~const` into `[const]`. After this we can remove the `~const` support from the parser
Caveat discovered during impl: there is no legacy bare trait object recovery for `[const] Trait` as that snippet in type position goes down the slice /array parsing code and will error
r? ``@fee1-dead``
cc ``@nikomatsakis`` ``@traviscross`` ``@compiler-errors``
Change const trait bound syntax from ~const to [const]2025-06-26T13:46:45+00:00Oli Scherergithub333195615777966@oli-obk.de2025-03-11T12:08:45+00:00urn:sha1:eb7245a864613f290c5668f4f4e8376edd065dc6compiler: Trim the misleading C of C-cmse from errors2025-06-25T07:52:10+00:00Jubilee Youngworkingjubilee@gmail.com2025-06-07T06:05:47+00:00urn:sha1:383d76106baa2042481de88dfff8ed2043ac50e6compiler: remove misleading 'c' from `abi_c_cmse_nonsecure_call` feature2025-06-25T07:52:10+00:00Jubilee Youngworkingjubilee@gmail.com2025-06-24T20:09:55+00:00urn:sha1:4bdf1c574a3b02daaf5793d71d089e94d192f57f