-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Remove remaining internal use of !Send
resources
#18386
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
Remove remaining internal use of !Send
resources
#18386
Conversation
I'm going to want @maniwani's eyes on this, hence the X-Controversial label. |
!Send
!Send
resources
The work on this PR is complete, but we are waiting for |
8b6d428
to
ec82c5f
Compare
Merging the linked PR for you :) |
ad60838
to
ec82c5f
Compare
Co-authored-by: Chris Russell <8494645+chescock@users.noreply.github.com>
…DAPTERS` Co-authored-by: Chris Russell <8494645+chescock@users.noreply.github.com>
ec82c5f
to
7bce0d2
Compare
Thank you so much for tackling this! I'm really happy that this is finally done, now we just need to remove the old |
Back to Waiting-on-Author until CI issues are resolved :( |
# Objective Remaining work for and closes bevyengine#17682. First half of work for that issue was completed in [PR 17730](bevyengine#17730). However, the rest of the work ended up getting blocked because we needed a way of forcing systems to run on the main thread without the use of `!Send` resources. That was unblocked by [PR 18301](bevyengine#18301). This work should finish unblocking the resources-as-components effort. # Testing Ran several examples using my Linux machine, just to make sure things are working as expected and no surprises pop up. --------- Co-authored-by: Chris Russell <8494645+chescock@users.noreply.github.com> Co-authored-by: François Mockers <francois.mockers@vleue.com>
Where's the migration guide for this PR? Also, why is WINIT_WINDOWS private? That's a huge breaking change. |
There are no changes that Bevy users should need to implement on their own. One can still use @IceSentry can you elaborate why |
Removing something that used to be public is a breaking change and needs a migration guide to inform users that this change happened even if it's just telling them they can't use it anymore. Also, if people were using those NonSend resources and still want to access them they need to know how to do it without having to dig through the codebase. Knowing that you need to add a special marker and access a global variable is not obvious.
I was working on a custom renderer and I needed to access the raw I was away for a while so I may have missed the discussion on discord. I recognize this is a very niche use case, but I was hit with it and it took me a while to figure out. |
Indeed: this 100% needs to be made public again and have a proper migration guide. Sorry for not spotting that in review. |
I see. Yes, this makes sense. Apologies for missing this. I'll work on a migration guide and make the resource replacements public. |
After removing `!Send` resources, `GILRS` and `WINIT_WINDOWS` were not made public, which is a breaking change. This was brought up in a [comment on that PR](#18386 (comment)). This PR makes them public. Fixes #19540.
Objective
Remaining work for and closes #17682. First half of work for that issue was completed in PR 17730. However, the rest of the work ended up getting blocked because we needed a way of forcing systems to run on the main thread without the use of
!Send
resources. That was unblocked by PR 18301.This work should finish unblocking the resources-as-components effort.
Testing
Ran several examples using my Linux machine, just to make sure things are working as expected and no surprises pop up.