-
Notifications
You must be signed in to change notification settings - Fork 258
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
refactor: use macros to derive merge_right
#1700
Comments
merge_right
merge_right
/bounty 100$ |
💎 $100 bounty created by tailcallhq 🙏 Thank you for contributing to tailcallhq/tailcall!.
|
/attempt
|
@ssddOnTop: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
From my findings, we'll need to keep the manual implementations for external types ( |
Yes. |
The bounty is up for grabs! Everyone is welcome to |
/attempt
|
💡 @Shylock-Hg submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
I have a draft locally but forgot to declare my attempt. In the queue 🤚🏽 |
@Shylock-Hg: You've been awarded a $100 bounty by tailcallhq! We'll notify you once it is processed. |
🎉🎈 @Shylock-Hg has been awarded $100! 🎈🎊 |
Currently
MergeRight
implementation is implemented by hand and is quite verbose. Let's use macro to reduce verbosity.Technical Requirements
tailcall-macros
to implement this procedural macro.trait MergeRight
intotailcall-macros
.merge_right
.Additional Information
You could start with something like:
Then, in
lib.rs
, you can start implementing your macro:The text was updated successfully, but these errors were encountered: