-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
FixedTime API should match Time directly #7439
Copy link
Copy link
Closed
Labels
A-TimeInvolves time keeping and reportingInvolves time keeping and reportingC-Code-QualityA section of code that is hard to understand or changeA section of code that is hard to understand or changeC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to use
Milestone
Description
What problem does this solve or what need does it fill?
(This issue discusses a post-#7267 Bevy: follow that PR for context.)
Migrating systems between CoreSet::Update and CoreSchedule::FixedUpdate should be painless.
In particular, Time and FixedTime should be one-for-one drop in replacements for each other.
What solution would you like?
Fully synchronize the methods available between Time and FixedTime.
Every method on one should be represented on the other wherever possible.
This can probably just be done manually to start.
What alternative(s) have you considered?
We could use a trait here, but I'm not sure the indirection / complexity is worth it.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-TimeInvolves time keeping and reportingInvolves time keeping and reportingC-Code-QualityA section of code that is hard to understand or changeA section of code that is hard to understand or changeC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to use