-
Notifications
You must be signed in to change notification settings - Fork 34
Added optional deref implementation for Getters #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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 problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I ask why you chose this option over something like
#[get ="deref"]or#[get = "pub deref"]?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was mostly to be coherent with the current implementation. The string associated with the attribute was the "visibility" of the function, so it was a bit strange to add the
derefpart there. I can change it, of course, but it was strange for me.Also, if we used the
derefin that place, would we allow#[get="deref pub"]? or only#[get="pub deref"]. What about complex visibility modifiers such as#[get="pub(crate)"]?It can be done, but i think it's a bit more cumbersome to define.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I'm not entirely sure I favor either way. One bother for me is that
#[get_mut] #[deref]seems odd. It makes#[deref]into a no-op. Also#[deref]alone would be a no-op.That said, I could see a legitimate use case under #21 .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, I thought about this more. I think we should take a conservative approach.
The goal of this library is to reduce the boilerplate associated with trivial getters and setters in a minimal fashion to support library evolution in a practical manner.
Notably: Field Access is not ABI stable across struct versions. Having Getters and Setters helps with stability.
Thankfully visibility modifiers are fairly easily tokenizable. We can create a simple set from the tokens present, and if
deref(which is not a valid visibility modifer) is present we can do this deref implementation.How does that sound to you?
I think ideal would be something like
#[get(vis = "pub", deref)]but at least when I tried a when I first wrote this it didn't seem possible.