-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Adding Copy, Clone, Debug
to derived traits of ExecutorKind
#9385
Adding Copy, Clone, Debug
to derived traits of ExecutorKind
#9385
Conversation
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
Clone
to derived traits of ExcutorKind
It is probably fine to derive |
Clone
to derived traits of ExcutorKind
Clone
to derived traits of ExecutorKind
Clone
to derived traits of ExecutorKind
Copy, Clone
to derived traits of ExecutorKind
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.
What's the consensus on throwing a Debug
in there as well? Any Bevy project level recommendation? (question for maintainers)
The merge failed, so there is still time for |
Copy, Clone
to derived traits of ExecutorKind
Copy, Clone, Debug
to derived traits of ExecutorKind
|
While being nobody other's issue as far I can tell, I want to create a trait I plan to implement on
App
where more than one schedule is modified.My workaround so far was working with a closure that returns an
ExecutorKind
from a match of the method variable.It makes it easier for me to being able to clone
ExecutorKind
and I don't see this being controversial for others working with Bevy.I did nothing more than adding
Clone
to the derived traits, no migration guide needed.(If this worked out then the GitHub editor is not too shabby.)