-
Notifications
You must be signed in to change notification settings - Fork 23
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
Provide ability to create getters that return A<&T>
instead of &A<T>
#78
Labels
Comments
This was referenced Feb 2, 2022
I'd be happy to implement this as the default for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for this awesome crate!
Getters that return
&Option<T>
(just like&Result<T>
, etc.) are not really useful, as they require getter user to pollute code with.as_ref()
everywhere. As alternative, having manual trivial getters likeis just another kind of boilerplate code pollution.
Can we do anything with this (and not some breaking change at the same time of course)?
I guess solution would likely require working with each such type separately (perhaps adding
OptionGetters
and#[get_option = "pub"]
, etc.), but still this would make this crate more coherent for users.The text was updated successfully, but these errors were encountered: