-
-
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
Implement Reflect for the remaining Range types #5763
Labels
A-Reflection
Runtime information about types
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
D-Trivial
Nice and easy! A great choice to get started with Bevy
Comments
ItsDoot
added
C-Feature
A new feature, making something new possible
S-Needs-Triage
This issue needs to be labelled
labels
Aug 22, 2022
Should also consider changing |
alice-i-cecile
added
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
A-Reflection
Runtime information about types
D-Trivial
Nice and easy! A great choice to get started with Bevy
and removed
C-Feature
A new feature, making something new possible
S-Needs-Triage
This issue needs to be labelled
labels
Aug 23, 2022
bors bot
pushed a commit
that referenced
this issue
Aug 30, 2022
# Objective Remove extra spaces from Range reflect impls. Follow up to #5763 ## Solution Remove extra spaces from Range reflect impls.
james7132
pushed a commit
to james7132/bevy
that referenced
this issue
Oct 28, 2022
# Objective Fixes bevyengine#5763 ## Solution Implemented as reflect value like the current `Range`. Is there a benefit to changing everything to a reflect struct?
james7132
pushed a commit
to james7132/bevy
that referenced
this issue
Oct 28, 2022
# Objective Remove extra spaces from Range reflect impls. Follow up to bevyengine#5763 ## Solution Remove extra spaces from Range reflect impls.
ItsDoot
pushed a commit
to ItsDoot/bevy
that referenced
this issue
Feb 1, 2023
# Objective Fixes bevyengine#5763 ## Solution Implemented as reflect value like the current `Range`. Is there a benefit to changing everything to a reflect struct?
ItsDoot
pushed a commit
to ItsDoot/bevy
that referenced
this issue
Feb 1, 2023
# Objective Remove extra spaces from Range reflect impls. Follow up to bevyengine#5763 ## Solution Remove extra spaces from Range reflect impls.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Reflection
Runtime information about types
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
D-Trivial
Nice and easy! A great choice to get started with Bevy
What problem does this solve or what need does it fill?
We have a Reflect impl for
Range
presently, but there are other range types that aren't covered:RangeInclusive
(what I'm looking for presently)RangeFrom
RangeTo
RangeToInclusive
RangeFull
(probably not needed TBH, but listed for exhaustiveness)What solution would you like?
Add
Reflect
impls for the types listed above.What alternative(s) have you considered?
Use
Range
instead, howeverRange
isn't always exactly correct for a given problem.The text was updated successfully, but these errors were encountered: