-
Notifications
You must be signed in to change notification settings - Fork 725
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
Attach follows_from() before constructing future #2686
base: master
Are you sure you want to change the base?
Conversation
Thanks for working on this!
There are tests for the Let me know if you have any more questions! |
Does this look like it is going in the right direction to you? |
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.
this looks good to me, thank you!
I think we can make the |
Head branch was pushed to by a user without write access
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.
looks good to me, provided CI passes!
It seems that the only thing left here is formatting. |
@matthiasbeyer if you don't mind selecting "Allow changes from maintainers", I'm happy to pull the branch and run |
This patch moves the calls to `follows_from()` on the attribute span _before_ the construction of the future, so that the arguments that are moved into the future are used before that move. Before this, the attributes needed to be `Copy`, so they could be moved into the future and then be used in the `follows_from()` call. This patch removes this (implicit) requirement. Suggested-by: Eliza Weisman <[email protected]> Signed-off-by: Matthias Beyer <[email protected]>
Signed-off-by: Matthias Beyer <[email protected]>
5faa414
to
d0055ab
Compare
Squashed the changes and ensured the changes in the commits are formatted. |
Hi! Can this be merged soon? |
Would this still be useful? |
Motivation
See #2650
Solution
Moving loop that makes the attribute span
follows_from()
other attribute spans before the creation of the future to remove the implicitCopy
requirement for attributes.CC @hawkw does this look right to you? How and where can I add a testcase for this ( I am a first time contributor to this project)?
CC @TheNeikos (submitted the issue mentioned above with me)