-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Bring back behavior of -Xfatal-warnings #19713
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
I can understand how it impedes your -Xprompt workflow (interesting to learn!). I definitely don't think we should diverge on behaviour between -Werror and -Xfatal-warnings. Ideally we can make -Xprompt react eagerly on a warning, while under fatal warnings. |
Workaround until then is using |
We decided to go in that direction because we wanted to make the flags enabling all the default errors (upcoming |
It might be simpler to make -Werror and -Xfatal-warinings behave differently. -Werror could emmit the single error on warning, while -Xfatal-warinings could make every warning an error. |
I think that's what But a bit of magic to turn |
Compiler version
Since #19245, -Xfatal-warning became completely useless to me. I critically rely on -Xfatal-warnings in connection with -Xprompt to stop the compilation at the point where a warning was given. I need this every other day. But with the new behavior, -Xfatal-warnings has become useless for this task, since it waits until the very end of the compilation run before anything is reported.
I don't see what the point of these disruptive things to the toolchain is. This change causes me to lose lots of time, and probably will cause problems for others relying on the old behavior as well.
We can institute new behavior for -Werror. But please, let's leave -Xfatal-warnings alone!
The text was updated successfully, but these errors were encountered: