-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Hard-to-read ICEs when fluent translation uses non-existing variable #128340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@rustbot label -needs-triage +C-enhancement +T-compiler +A-translation +D-diagnostic-infra |
...Honestly I feel like this should not even ICE. |
as we discussed, seems we need static analysis in tidy. |
Also note that the code that caused the ICE for me doesn't even use diagnostic types, it passes arguments to fluent manually. Even the suggested static analysis would not catch that. |
This is still painful. I'm 10 minutes into debugging why Fluent makes my patch ICE and I haven't got a clue. All I have is:
Something seems to be wrong with EDIT: Ah, I had to write I'd really appreciate if someone who knows and understands fluent could push the integration to a point where it doesn't actively slow down diagnostic work any more. The current limbo state is not sustainable. Cc @davidtwco I think? |
When I screw up the variable names in a messages.flt file, I am getting the following error:
Needless to say, this is not exactly a pleasant debugging experience. Would be nice to get a clear message saying what went wrong. :)
In this case, the string
const_eval_pointer_out_of_bounds
referenced$pointer_xx
which does not exist.The text was updated successfully, but these errors were encountered: