Reduce boilerplate code with macros - #61
Merged
Merged
Conversation
Member
Author
|
Currently, property handles have to be exposed to the user during building. However, I may have an idea to solve this too 🤔 |
tim-hellhake
approved these changes
Dec 31, 2021
tim-hellhake
left a comment
Member
There was a problem hiding this comment.
That will save a lot of typing 😬
Member
Author
|
PR description updated |
Member
Author
|
When rust-lang/rust#29635 was stabilized, we wouldn't even need the proc macro for this, but could simply provide a generic wrapper struct |
bewee
marked this pull request as ready for review
January 6, 2022 19:15
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
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.
This suggests splitting
xxx_handle_mut()functions into separate traits, and adding functionsxxx_handle()to these which return an immutable references. A proc macro can then be used to auto-implement these traits, including adding a field holding the handle to the struct.Ultimately, this should also unify the code by wrapping EventHandles in Events, and adding an APIHandlerHandle. Solely the Action would remain different (would they?).
Examples
is equivalent to
and is equivalent to previously doing