Add error-prone rule for converting Stream to Iterator #3058
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.
Before this PR
In certain cases (https://bugs.openjdk.org/browse/JDK-8267359) converting Stream to Iterator can cause the entire stream to be consumed eagerly. This has bitten us on multiple occasions, causing poor performance in otherwise innocuous code.
Catching the specific cases isn't easy, but just generally converting between the two iteration paradigms is a code smell and should be avoided where possible, so let's warn against it.
After this PR
==COMMIT_MSG==
Add error-prone rule for converting Stream to Iterator
==COMMIT_MSG==