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
In #18301,
NonSendMarker
was defined in such a way that it actually implementsSend
. This isn't strictly a soundness issue, as its goal is to be used as aSystemParam
, and it does appropriately mark system access as!Send
. It just seems odd thatNonSendMarker: Send
.Solution
NonSendMarker
wrapPhantomData<*mut ()>
, which forces it to be!Send
.Testing
Notes
This does mean constructing a
NonSendMarker
value will require using theSystemParam
trait, but I think that's acceptable as the marker as a value should be rarely required if at all.