diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-27 22:13:00 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-27 22:13:00 +0200 |
| commit | 36c2b011cb4bb9bd34647486551e85a969773c8d (patch) | |
| tree | e3b6cf9615355244e05cb699f6d3896217179a0c /compiler/rustc_pattern_analysis/src/errors.rs | |
| parent | fe5f3dedf7b4d6bea2cadb17343f747d70b4c66b (diff) | |
| parent | 512ff9520666a952850d0a360a4310c5995f6991 (diff) | |
| download | rust-36c2b011cb4bb9bd34647486551e85a969773c8d.tar.gz rust-36c2b011cb4bb9bd34647486551e85a969773c8d.zip | |
Rollup merge of #139858 - oli-obk:new-const-traits-syntax, r=fee1-dead
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``
Diffstat (limited to 'compiler/rustc_pattern_analysis/src/errors.rs')
0 files changed, 0 insertions, 0 deletions