Better diagnostics for map iteration while mutating #10
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.
If one obtains a
MutableMap.Entry
from a mutable map / builder, and then removes the underlying value from the map, we currently returnnull
from the entry'svalue
property, rather than throwing. Either behavior is allowed by theMutableMap.Entry
spec, which specifiesIllegalStateException
or undefined behavior in this case - but it's much easier to debug this if an exception is thrown.