Skip to content

interpret: go back to regular string interpolation for error messages#153611

Merged
rust-bors[bot] merged 3 commits intorust-lang:mainfrom
RalfJung:interp-error-strings
Mar 12, 2026
Merged

interpret: go back to regular string interpolation for error messages#153611
rust-bors[bot] merged 3 commits intorust-lang:mainfrom
RalfJung:interp-error-strings

Conversation

@RalfJung
Copy link
Member

@RalfJung RalfJung commented Mar 9, 2026

Using the translatable diagnostic infrastructure adds a whole lot of boilerplate which isn't actually useful for const-eval errors, so let's get rid of it. This effectively reverts #111677. That PR effectively added 1000 lines and this PR only removes around 600 -- the difference is caused by (a) keeping some of the types around for validation, where we can use them to share error strings and to trigger the extra help for pointer byte shenanigans during CTFE, and (b) this not being a full revert of #111677; I am not touching diagnostics outside the interpreter such as all the const-checking code which also got converted to fluent in the same PR.

The last commit does something similar for LayoutError, which also helps deduplicate a bunch of error strings. I can make that into a separate PR if you prefer.

r? @oli-obk
Fixes #113117
Fixes #116764
Fixes #112618

@rustbot
Copy link
Collaborator

rustbot commented Mar 9, 2026

Some changes occurred to the CTFE / Miri interpreter

cc @rust-lang/miri

The Miri subtree was changed

cc @rust-lang/miri

Some changes occurred to the CTFE machinery

cc @oli-obk, @lcnr

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

Some changes occurred to the CTFE / Miri interpreter

cc @rust-lang/miri, @oli-obk, @lcnr

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Mar 9, 2026
@rustbot
Copy link
Collaborator

rustbot commented Mar 9, 2026

oli-obk is not on the review rotation at the moment.
They may take a while to respond.

@RalfJung RalfJung force-pushed the interp-error-strings branch from caa7de3 to d42a68b Compare March 9, 2026 14:38
@rustbot

This comment has been minimized.

Comment on lines -1026 to -1027
AlignFromBytesError::NotPowerOfTwo(align) => write!(f, "`{align}` is not a power of 2"),
AlignFromBytesError::TooLarge(align) => write!(f, "`{align}` is too large"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally prefer this with the backticks

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are just numbers. We don't usually render them with backticks. And in fact they were not rendered with backticks in const-eval errors before, only in JSON errors. I changed the strings here to avoid changing the const-eval error output.

@RalfJung RalfJung force-pushed the interp-error-strings branch from a2139d5 to a060599 Compare March 9, 2026 15:06
TooLarge(u64),
}

impl AlignFromBytesError {
Copy link
Member Author

@RalfJung RalfJung Mar 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The AlignFromBytesError type got added #111677. Reverting that PR would mean replacing it by String again, but it actually seems reasonable to have a proper error type here so I decided to keep the type, but simplify and deduplicate the logic for turning it into a user-visible message.

@rust-log-analyzer

This comment has been minimized.

@RalfJung RalfJung force-pushed the interp-error-strings branch from a060599 to 66fbaa6 Compare March 9, 2026 16:46
@rustbot
Copy link
Collaborator

rustbot commented Mar 9, 2026

Some changes occurred in compiler/rustc_codegen_gcc

cc @antoyo, @GuillaumeGomez

@rustbot rustbot added the A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. label Mar 9, 2026
@GuillaumeGomez
Copy link
Member

This is MUCH better, thanks a lot!

@RalfJung RalfJung force-pushed the interp-error-strings branch 2 times, most recently from fa2e674 to 5cf0904 Compare March 9, 2026 17:55
@rust-log-analyzer

This comment has been minimized.

@RalfJung RalfJung force-pushed the interp-error-strings branch from 5cf0904 to 86315e9 Compare March 9, 2026 19:23
@rust-bors

This comment has been minimized.

@RalfJung RalfJung force-pushed the interp-error-strings branch from 86315e9 to e50b65c Compare March 9, 2026 20:52
@rustbot

This comment has been minimized.

Copy link
Contributor

@oli-obk oli-obk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 11, 2026

📌 Commit e50b65c has been approved by oli-obk

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 11, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors bot removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Mar 11, 2026
@RalfJung RalfJung force-pushed the interp-error-strings branch from e50b65c to fe1f92a Compare March 11, 2026 12:55
@rustbot
Copy link
Collaborator

rustbot commented Mar 11, 2026

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@RalfJung
Copy link
Member Author

@bors r=oli-obk

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 11, 2026

📌 Commit fe1f92a has been approved by oli-obk

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 11, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 11, 2026
…li-obk

interpret: go back to regular string interpolation for error messages

Using the translatable diagnostic infrastructure adds a whole lot of boilerplate which isn't actually useful for const-eval errors, so let's get rid of it. This effectively reverts rust-lang#111677. That PR effectively added 1000 lines and this PR only removes around 600 -- the difference is caused by (a) keeping some of the types around for validation, where we can use them to share error strings and to trigger the extra help for pointer byte shenanigans during CTFE, and (b) this not being a full revert of rust-lang#111677; I am not touching diagnostics outside the interpreter such as all the const-checking code which also got converted to fluent in the same PR.

The last commit does something similar for `LayoutError`, which also helps deduplicate a bunch of error strings. I can make that into a separate PR if you prefer.

r? @oli-obk
Fixes rust-lang#113117
Fixes rust-lang#116764
Fixes rust-lang#112618
rust-bors bot pushed a commit that referenced this pull request Mar 11, 2026
…uwer

Rollup of 9 pull requests

Successful merges:

 - #153571 (Avoid ICE when an EII declaration conflicts with a constructor)
 - #153581 (Simplify `type_of_opaque`.)
 - #153611 (interpret: go back to regular string interpolation for error messages)
 - #153635 (Unify same-span labels in move error diagnostics)
 - #153660 (mir-opt: Drop invalid debuginfos after SingleUseConsts.)
 - #153685 (Introduce `for_each_query_vtable!` to move more code out of query macros)
 - #153671 (Make Enzyme has dependent on LLVM hash)
 - #153710 (remove `.ftl` checks from tidy)
 - #153720 (doc/rustc: clarify how to contact arm-maintainers)
rust-bors bot pushed a commit that referenced this pull request Mar 11, 2026
…uwer

Rollup of 9 pull requests

Successful merges:

 - #153571 (Avoid ICE when an EII declaration conflicts with a constructor)
 - #153581 (Simplify `type_of_opaque`.)
 - #153611 (interpret: go back to regular string interpolation for error messages)
 - #153635 (Unify same-span labels in move error diagnostics)
 - #153660 (mir-opt: Drop invalid debuginfos after SingleUseConsts.)
 - #153685 (Introduce `for_each_query_vtable!` to move more code out of query macros)
 - #153671 (Make Enzyme has dependent on LLVM hash)
 - #153710 (remove `.ftl` checks from tidy)
 - #153720 (doc/rustc: clarify how to contact arm-maintainers)
rust-bors bot pushed a commit that referenced this pull request Mar 11, 2026
…uwer

Rollup of 9 pull requests

Successful merges:

 - #153571 (Avoid ICE when an EII declaration conflicts with a constructor)
 - #153581 (Simplify `type_of_opaque`.)
 - #153611 (interpret: go back to regular string interpolation for error messages)
 - #153635 (Unify same-span labels in move error diagnostics)
 - #153660 (mir-opt: Drop invalid debuginfos after SingleUseConsts.)
 - #153685 (Introduce `for_each_query_vtable!` to move more code out of query macros)
 - #153671 (Make Enzyme has dependent on LLVM hash)
 - #153710 (remove `.ftl` checks from tidy)
 - #153720 (doc/rustc: clarify how to contact arm-maintainers)
rust-bors bot pushed a commit that referenced this pull request Mar 11, 2026
…uwer

Rollup of 12 pull requests

Successful merges:

 - #152569 (Stop using rustc_layout_scalar_valid_range_* in rustc)
 - #153421 (Fix ICE in fn_delegation when child segment resolves to a trait)
 - #153571 (Avoid ICE when an EII declaration conflicts with a constructor)
 - #153581 (Simplify `type_of_opaque`.)
 - #153611 (interpret: go back to regular string interpolation for error messages)
 - #153635 (Unify same-span labels in move error diagnostics)
 - #153660 (mir-opt: Drop invalid debuginfos after SingleUseConsts.)
 - #153685 (Introduce `for_each_query_vtable!` to move more code out of query macros)
 - #153722 (miri-test-libstd: use --tests and update some comments)
 - #153671 (Make Enzyme has dependent on LLVM hash)
 - #153710 (remove `.ftl` checks from tidy)
 - #153720 (doc/rustc: clarify how to contact arm-maintainers)
@rust-bors rust-bors bot merged commit 77134bd into rust-lang:main Mar 12, 2026
11 checks passed
@rustbot rustbot added this to the 1.96.0 milestone Mar 12, 2026
github-actions bot pushed a commit to rust-lang/miri that referenced this pull request Mar 12, 2026
…uwer

Rollup of 12 pull requests

Successful merges:

 - rust-lang/rust#152569 (Stop using rustc_layout_scalar_valid_range_* in rustc)
 - rust-lang/rust#153421 (Fix ICE in fn_delegation when child segment resolves to a trait)
 - rust-lang/rust#153571 (Avoid ICE when an EII declaration conflicts with a constructor)
 - rust-lang/rust#153581 (Simplify `type_of_opaque`.)
 - rust-lang/rust#153611 (interpret: go back to regular string interpolation for error messages)
 - rust-lang/rust#153635 (Unify same-span labels in move error diagnostics)
 - rust-lang/rust#153660 (mir-opt: Drop invalid debuginfos after SingleUseConsts.)
 - rust-lang/rust#153685 (Introduce `for_each_query_vtable!` to move more code out of query macros)
 - rust-lang/rust#153722 (miri-test-libstd: use --tests and update some comments)
 - rust-lang/rust#153671 (Make Enzyme has dependent on LLVM hash)
 - rust-lang/rust#153710 (remove `.ftl` checks from tidy)
 - rust-lang/rust#153720 (doc/rustc: clarify how to contact arm-maintainers)
@RalfJung RalfJung deleted the interp-error-strings branch March 12, 2026 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

6 participants