Added support for System.Collection.Frozen-types - #1750
Closed
N-Olbert wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Closed, since already done by #1730 (should have pulled before 👍 ) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds support for
System.Collections.Frozen.FrozenSet<T>andSystem.Collections.Frozen.FrozenDictionary<TKey, TValue>.The implementation is very similar to that of the ImmutableCollectionResolver.
Internally, the data will be de-/serialized like a normal
HashSet/Dictionaryand eventually transformed into a frozen collection. Since neither sets nor (non-ordered-)dictionaries enforce ordering, any possible shuffling during de-/serialization is irrelevant.Fixes #1720