-
-
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
[ecs] Split DetectChanges
into SetChanged
#2330
[ecs] Split DetectChanges
into SetChanged
#2330
Conversation
It looks like we'll need to eventually introduce a trait for getting the value of a thing that implements change detection. Ideally I'd like to build that PR on top of this one, so I'll try to push for this to get merged soon. :) |
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.
Interesting. I think I'm in favor of this refactor.
It's a little strange to me that |
51da589
to
c9b16ed
Compare
Sorry for being dormant on this PR, I just pushed some changes and rebased onto main. |
This has currently conflicts due to #2345. |
Thanks for reminding me about this @MinerSebas ! |
6dcf833
to
67c81d8
Compare
No longer needed; closing this out :) |
Objective
DetectChanges
however that did not cover the use case for immutable change detection (such asRes<T>
)Solution
DetectChanges
to also have aSetChanged
trait where theSetChanged
trait is only implemented for the mutable change detection structs.