Skip to content
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

Warnings should not be emitted if constant is expected to be missing #337

Open
mmarchini opened this issue Feb 13, 2020 · 0 comments
Open

Comments

@mmarchini
Copy link
Contributor

Some constants are expected to be missing in some versions, but they'll warn anyway. This is problematic because it pollutes the warnings, making it harder to know when a constant is actually missing. Missing constants should still warn when they are expected to be missing, but they should fail silently otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant