Migrate the CollectionStreamForEach refactor to error-prone #1139
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
Generate changelog in
|
Contributor
Author
|
Verified on a large internal project |
ferozco
approved these changes
Jan 2, 2020
This was referenced Jan 8, 2020
This was referenced Jan 8, 2020
This was referenced Jan 16, 2020
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.
==COMMIT_MSG==
Migrate the CollectionStreamForEach refactor to error-prone
==COMMIT_MSG==
Possible downsides?
Previously this was not merge blocking, but the updated check will fail compilation for projects which fail on warnings.
There's a potential failure scenario where a collection implementation can define forEach using
this.stream(), however that code should be rewritten to avoid stream overhead.