feat: forbid most collections from containing zst elements/keys #202
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.
Part of #51 . (initially change caused by RUSTSEC-2023-0033)
Addressing review comment:
VecDeque, LinkedList, HashSet and BTreeSet have all been performing zst check during deserialization implicitly.
This pr adds corresponding checks to their serialization methods for consistency.
HashMap and BTreeMap have been performing this implicit check for
(K, V)
type.A more strict check for only the key type in maps was added in the pr according to the mention in comment.
Check for arrays wasn't added, as there is a test, which asserts, that zsts are acceptable.