fix: borrow semantics - #72
Open
sansmoraxz wants to merge 4 commits into
Open
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
…ept borrowed keys
Author
Oops my bad, actually some generated methods didn't use the borrow based lookup. |
Author
|
cc @lun3x |
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.
There was a misunderstanding from the README.No wait only simple getters were borrow, not get mutators, modifiers or removers.We don't need to pass owned references into the getter, slice types works ie pass
&strinstead of&String.Public API is now uniform for borrowed keys.
Resolves: #71