feat(keyPath): Use WritableKeyPath instead of KeyPath
#50
Conversation
This file contains 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
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.
⚽️ Description
Require usage of
WritableKeyPath. Until now we were relying on UnsafeMutablePointer to transform Keypath as mutable/writable.This made the code more complex and it probably makes to say that only entities defined as var are writable.
This opens up simpler solutions for adopting support for enum.
If we ever need we'll go back to old implementation but I don't expect so and for now... let's keep things as simple as possible.
🔨 Implementation details
UnsafeMutablePointerextensionBufferedCollectionKeyPathbyWritableKeyPath