You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
finish and clean up rustc_const_eval's translatable diagnostics. #113117
In #111677 I added a trait called ReportErrorExt which should be replaced by implementing IntoDiagnostic for newtypes. Another thing would be to investigate if the same can be done for MachineStopType which requires being made into a trait object.
this is an example of using fluent's pattern matching for different error messages. These should be eventually replaced by individual messages with their own identifiers instead of pattern matching.
I'll assign this to myself when I get time. Feel free to claim if this is unassigned.
this is an example of using fluent's pattern matching for different error messages. These should be eventually replaced by individual messages with their own identifiers instead of pattern matching.
That link doesn't seem to work here. What are you referring to?
The next step then probably is to entirely remove the use of fluent for const-eval errors: we already have our own error types providing the benefits people ascribe to error structs (I think); we should just go back to translating those error types directly into strings IMO.
Activity
victor-timofei commentedon Jun 30, 2023
@rustbot claim
I would love to help with this
fee1-dead commentedon Jun 30, 2023
Hi @victor-timofei, thanks for claiming this! Feel free to open a thread on Zulip and ping me if you get stuck.
RalfJung commentedon Aug 19, 2023
That link doesn't seem to work here. What are you referring to?
fee1-dead commentedon Aug 19, 2023
See this
CastilloDel commentedon Oct 24, 2024
@rustbot claim
CastilloDel commentedon Oct 24, 2024
@rustbot release-assignment
JayanAXHF commentedon Jan 11, 2026
Is this issue still open to contribution?
RalfJung commentedon Jan 11, 2026
Let's wait until rust-lang/compiler-team#959 is resolved before doing anything here.
The next step then probably is to entirely remove the use of fluent for const-eval errors: we already have our own error types providing the benefits people ascribe to error structs (I think); we should just go back to translating those error types directly into strings IMO.
Rollup merge of rust-lang#153611 - RalfJung:interp-error-strings, r=o…
Rollup merge of rust-lang#153611 - RalfJung:interp-error-strings, r=o…
Rollup merge of #153611 - RalfJung:interp-error-strings, r=oli-obk