-
-
Notifications
You must be signed in to change notification settings - Fork 4k
Assets::get_many
#19484
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?
Assets::get_many
#19484
Conversation
I think we should do this; Contentious is just for the use of |
i dont understand why the ci is failing now |
This is broken at head currently https://discord.com/channels/691052431525675048/692572690833473578/1381857479520161803 I believe we're still trying to work out a fix. |
Related issue: #19573 |
fixes #16244
Assets<A>
should have get_many / get_many_mut functions just likeQuery<...>
does.thats why I took the implementation of get_many_mut for
Query
as an inspiration.i had to add an
#[allow(unsafe_code)]
above get_many_mut, so i want to know if thats permitted at that locationthis pr also makes #16334 obsolete
Testing
I added two unit tests for get_many_mut (since get_many is trivial), but ill happily write more if there are some edge cases i overlooked (unsafe code is scarry)