-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Merged by Bors] - Allow Option<NonSend<T>> and Option<NonSendMut<T>> as SystemParam #2345
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This does currently conflict with #2330 as it changes/moves |
NathanSWard
added
A-ECS
Entities, components, systems, and events
C-Feature
A new feature, making something new possible
and removed
S-Needs-Triage
This issue needs to be labelled
labels
Jun 15, 2021
This looks good to me! |
NathanSWard
approved these changes
Jun 15, 2021
mockersf
approved these changes
Jun 15, 2021
mockersf
added
the
S-Ready-For-Final-Review
This PR has been approved by the community. It's ready for a maintainer to consider merging it
label
Jun 15, 2021
bors r+ |
bors bot
pushed a commit
that referenced
this pull request
Jun 26, 2021
) # Objective Currently, you can add `Option<Res<T>` or `Option<ResMut<T>` as a SystemParam, if the Resource could potentially not exist, but this functionality doesn't exist for `NonSend` and `NonSendMut` ## Solution Adds implementations to use `Option<NonSend<T>>` and Option<NonSendMut<T>> as SystemParams.
Pull request successfully merged into main. Build succeeded: |
bors
bot
changed the title
Allow Option<NonSend<T>> and Option<NonSendMut<T>> as SystemParam
[Merged by Bors] - Allow Option<NonSend<T>> and Option<NonSendMut<T>> as SystemParam
Jun 26, 2021
This was referenced Jun 28, 2021
ostwilkens
pushed a commit
to ostwilkens/bevy
that referenced
this pull request
Jul 27, 2021
…vyengine#2345) # Objective Currently, you can add `Option<Res<T>` or `Option<ResMut<T>` as a SystemParam, if the Resource could potentially not exist, but this functionality doesn't exist for `NonSend` and `NonSendMut` ## Solution Adds implementations to use `Option<NonSend<T>>` and Option<NonSendMut<T>> as SystemParams.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-ECS
Entities, components, systems, and events
C-Feature
A new feature, making something new possible
S-Ready-For-Final-Review
This PR has been approved by the community. It's ready for a maintainer to consider merging it
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Currently, you can add
Option<Res<T>
orOption<ResMut<T>
as a SystemParam, if the Resource could potentially not exist, but this functionality doesn't exist forNonSend
andNonSendMut
Solution
Adds implementations to use
Option<NonSend<T>>
and Option<NonSendMut> as SystemParams.