Issue 4: sparse declarative defaults #5
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.
Declarative defaults now handle sparseness
A fix for #4. The old way of setting
SparseEnumap
defaults (SparseEnumap.set_defaults(...)
) handled sparseness correctly. That is, callingset_defaults(*args, **kwargs)
created a defaults dictionary withNone
placeholders. For example:The declarative version:
... was broken. Each member in a
SparseEnumap
should have a default no matter what.