Use map instead of mapValues/shuffle in XMLCoderElement.flatten #93
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.
This PR uses a
map
overkey
-value
pairs instead ofmapValues
along withshuffled()
when transforming attributes into aBox
-ed representation withinXMLCoderElement.flatten()
.At first, I was wondering what the
shuffled()
was for. I tried to get rid of it on its own, but the compiler didn't appreciate that very much when it came toKeyedStorage.init<S>(_ sequence: S) where S: Sequence, S.Element == (Key, Value)
. Could this be a moment of ambiguity between(Key,Value)
and(key: Key, value: Value)
?Ultimately,
mapValues
alone should do the trick, but I thought it might be nice to avoid another O(n) pass if not necessary.Did
shuffled
have any other purpose than juggling types with the compiler?