-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Input uses references when possible #14182
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
base: main
Are you sure you want to change the base?
Input uses references when possible #14182
Conversation
41b19fd
to
acf804a
Compare
acf804a
to
a781fe6
Compare
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.
Wondering if this needs a Migration note since some public signatures changed.
yes it should... But I'm not sure I like this PR. It's the right thing to do, but there soo many additional |
cdfe4f6
to
57c3dd9
Compare
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
Has merge conflicts, waiting on migration guide |
Objective
T
instead of&T
Solution
Not using references is mostly not a problem in Bevy because most build in inputs are small types. It feels more correct to take references and it will be better for larger input types