Avoid redundant shallow copy when getting read-only map fields #741
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.
_FieldSet._$getMap
unnecessarily shallow-copies the map field when themessage is read-only.
If a message is read-only then all of its fields are read-only, so the
map fields are read-only. We don't need to copy them.
Copying map fields on every access can be expensive depending on the map
size, so this will potentially be a significant performance win.
(Also, if we had to copy, we would have to deep-copy, rather than
shallow-copy, so the code would be buggy if we needed to copy the field)
Also fix
_isReadonly
field initialization inPbMap.unmodifiable
.We actually do not use
PbMap.unmodifiable
and we don't have any usersof it, but I think that method will be useful when fixing #705, so I'm
not removing it for now.