Skip to content

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

Open
RalfJung wants to merge 3 commits intorust-lang:mainfrom
RalfJung:interp-error-strings
Open

interpret: go back to regular string interpolation for error messages#153611
RalfJung wants to merge 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
Copy link
Collaborator

rustbot commented Mar 9, 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.

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-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.

Projects

None yet

6 participants