We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#47879 indicates that this should have been added in 16.9, but it was missed.
Related to #47841 and #47879
@jaredpar @cston Can this be added now to warning level 5 or is it too late? I don't know what your policy is for adding new warnings to warning waves.
The text was updated successfully, but these errors were encountered:
At this point it would need to be in a new warning wave. The current wave is essentially locked.
Not a huge deal though. We're doing a new wave with ever language version so it can just tack into the new one.
Sorry, something went wrong.
To be clear, this is something we'd now like to do in wave 6, right?
Yes.
@jaredpar Is this something that can go into features/compiler branch now?
Closing. Fixed in #53352
Successfully merging a pull request may close this issue.
#47879 indicates that this should have been added in 16.9, but it was missed.
Related to #47841 and #47879
@jaredpar @cston Can this be added now to warning level 5 or is it too late? I don't know what your policy is for adding new warnings to warning waves.
The text was updated successfully, but these errors were encountered: