-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Proposal: New simpler onwarn
API
#2040
Comments
Another radical, even simpler idea: No |
I like the second idea, it makes a lot of sense |
closed via #2093 |
As discussed in chat, it may be nice to simplify the
onwarn
callback API. Currently, it accepts two arguments, a warning object and the default onwarn handler. Consumers can inspect the warning object and decide whether and how to call the default onwarn handler.Instead, it could just accept a warning object, and return a boolean, indicating whether the compiler should display this warning. Slightly less powerful (but I don't see any real uses for the power we would use), and simpler to understand.
The text was updated successfully, but these errors were encountered: