Repository navigation
Strip all leading asterisks in DanglingDocCommentToBlockComment (C9 of #1330) - #1364
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes C9 of #1330.
DanglingDocCommentToBlockCommentstripped a single*per cycle, so a banner like/******** section ********/never converged: each run turned it into another doc comment with one asterisk less. The recipe now strips the whole leading run of asterisks.Skipping banners instead was not an option, as javac 25 with
-Xlint:dangling-doc-commentsflags/***/,/*** three ***/and/******** section ********/just like/**; I checked that, and that the rewritten/**/,/* section ********/and multi-line/*forms compile without the warning.Verified with
./gradlew test --tests DanglingDocCommentToBlockCommentTest(10 tests, all passing), including a newbannerstest.