Use array for SetShape #172
Merged
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.
Issue #, if available:
We decided to use Array for SetShape in internal discussions for similar reasons to why Objects are used instead of Map:
new Set()
, just likenew Map()
setObj.has(value)
is similar toobjMap.get(key)
Smithy specification for Set https://awslabs.github.io/smithy/spec/core.html#set
Not all languages support set data structures with non-scalar values. Such languages SHOULD represent sets as a custom set data structure that can interpret value hash codes and equality. Alternatively, clients MAY store the values of a set data structure in a list and rely on the service to ensure uniqueness.
Description of changes:
Use array for SetShape
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.