-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Compiler error when using iter_combinations with filtered query #3651
Comments
This is just a bug, rather than a known limitation. I suspect that just adding the appropriate |
Yep, seems like adding a If nobody else gets to this in the next couple weeks I'll pick it up. |
harudagondi
added a commit
to harudagondi/bevy
that referenced
this issue
Jan 13, 2022
harudagondi
added a commit
to harudagondi/bevy
that referenced
this issue
Jan 13, 2022
harudagondi
added a commit
to harudagondi/bevy
that referenced
this issue
Jan 13, 2022
aevyrie
pushed a commit
to aevyrie/bevy
that referenced
this issue
Jun 7, 2022
# Objective - Previously, `iter_combinations()` does not work on queries that have filters. - Fixes bevyengine#3651 ## Solution - Derived Copy on all `*Fetch<T>` structs, and manually implemented `Clone` to allow the test to pass (`.count()` does not work on `QueryCombinationIter` when `Clone` is derived) Co-authored-by: Carter Anderson <[email protected]>
ItsDoot
pushed a commit
to ItsDoot/bevy
that referenced
this issue
Feb 1, 2023
# Objective - Previously, `iter_combinations()` does not work on queries that have filters. - Fixes bevyengine#3651 ## Solution - Derived Copy on all `*Fetch<T>` structs, and manually implemented `Clone` to allow the test to pass (`.count()` does not work on `QueryCombinationIter` when `Clone` is derived) Co-authored-by: Carter Anderson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bevy version
0.6
main
What you did
What actually happened
What you expected to happen
No compiler error.
Or if this is a known limitation or intended or something special needs to be done to make this work, some documentation pointing that out.
The text was updated successfully, but these errors were encountered: