-
-
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
[Merged by Bors] - Fix Option<NonSend<T>> and Option<NonSendMut<T>> #2757
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 reverts commit e553e4e.
alice-i-cecile
added
A-ECS
Entities, components, systems, and events
C-Bug
An unexpected or incorrect behavior
and removed
S-Needs-Triage
This issue needs to be labelled
labels
Aug 31, 2021
The comment fixes look like this got pulled in from a different PR perhaps? They look good to merge, but it would be cleaner with just the two fix commits and the tests in there. |
yea thats true, fixed that. |
mockersf
approved these changes
Aug 31, 2021
alice-i-cecile
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
Aug 31, 2021
alice-i-cecile
approved these changes
Aug 31, 2021
bors r+ |
bors bot
pushed a commit
that referenced
this pull request
Aug 31, 2021
# Objective Fix `Option<NonSend<T>>` to work when T isn't `Send` Fix `Option<NonSendMut<T>>` to work when T isnt in the world. ## Solution Simple two row fix, properly initialize T in `OptionNonSendState` and remove `T: Component` bound for `Option<NonSendMut<T>>` also added a rudimentary test Co-authored-by: Ïvar Källström <[email protected]>
bors
bot
changed the title
Fix Option<NonSend<T>> and Option<NonSendMut<T>>
[Merged by Bors] - Fix Option<NonSend<T>> and Option<NonSendMut<T>>
Aug 31, 2021
bilsen
added a commit
to bilsen/bevy
that referenced
this pull request
Sep 2, 2021
# Objective Fix `Option<NonSend<T>>` to work when T isn't `Send` Fix `Option<NonSendMut<T>>` to work when T isnt in the world. ## Solution Simple two row fix, properly initialize T in `OptionNonSendState` and remove `T: Component` bound for `Option<NonSendMut<T>>` also added a rudimentary test Co-authored-by: Ïvar Källström <[email protected]>
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-Bug
An unexpected or incorrect behavior
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
Fix
Option<NonSend<T>>
to work when T isn'tSend
Fix
Option<NonSendMut<T>>
to work when T isnt in the world.Solution
Simple two row fix, properly initialize T in
OptionNonSendState
and removeT: Component
bound forOption<NonSendMut<T>>
also added a rudimentary test