-
Notifications
You must be signed in to change notification settings - Fork 300
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
Implement trait deriving for RustAutoOpaque (Clone, Debug, PartialEq, Eq) #2272
Comments
I guess there are several separated issues here
Since this looks not hard (several lines of code), again, feel free to PR! Alternatively I may work on it later if you explicitly not do it :) |
Just a double check: Do you want to have fun PR for this? If so I will leave it to you, if not I will make a small PR ;) |
Thanks for asking :) I was about to approach it - but then wanted to get the other PRs done first ... I am taking care of the logging now (investigating I guess you are done by then with this PR, so please go ahead! Thanks! |
Btw, |
Great that you already implemented it! Thanks! |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue. |
Describe the bug
leads to the compiler error
Steps to reproduce
Logs
see the error in the description
Expected behavior
RustAutoOpaque goes out of the way and uses the underlying type's derived traits.
Generated binding code
No response
OS
No response
Version of
flutter_rust_bridge_codegen
No response
Flutter info
No response
Version of
clang++
No response
Additional context
A workaround is to implement the traits on the wrapped type, for example
needs to wrap the string, so we can implement a trait
and then implement the missing trait
While Clone is needed (even if not called, see #2244 (comment)), the other traits are more of a "nice to have".
It should be as easy as
though the devil might be in the details :)
Having
might be sufficient for now :)
The text was updated successfully, but these errors were encountered: