[PoC][Concurrency] Proof out and simulate "send" semantics #62213
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
ktoso
added
the
concurrency
|
@swift-ci please smoke test |
ktoso
commented
Nov 21, 2022
| fputs("spawn:\(iteration)\n", stderr) | ||
|
|
||
|
|
||
| self.send { |
There was a problem hiding this comment.
If this was Task{} the order of those executions is not guaranteed, and the test would crash on the precondition below.
ktoso
changed the title
ktoso
commented
Dec 22, 2022
|
Will be replaced with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The same test if implemented with
Task{}will crash as the order of the enqueues is not guaranteed.This is just a silly PoC to showcase how a send-like semantics enqueue order improves on the status quo of working with actors when deterministic order is expected.