Allow warning-ignore in the same line as the respective warning #47863
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch allows putting
warning-ignore
comments in the same line as the respective warning itself.I can't think of any particular reason the latter shouldn't be allowed.
It should be up to the programmer to decide where to put their comments.
Personally, and I'm sure I'm not the only one, I find the latter more readable as it doesn't visually interrupt the actual code.
I took a look at the source and saw that this fix only requires a
>=
to be changed to>
, so this is a very simple fix for slightly more flexibility.As for the master branch, I couldn't find any code related to honoring
warning-ignore
at all, so this fix is only for 3.x versions.