add yielding IO back-end for turso-stress to test async re-entrancy#7377
Open
PThorpe92 wants to merge 4 commits into
Open
add yielding IO back-end for turso-stress to test async re-entrancy#7377PThorpe92 wants to merge 4 commits into
PThorpe92 wants to merge 4 commits into
Conversation
jussisaurio
approved these changes
Jun 5, 2026
Collaborator
|
@PThorpe92 Let's instead add another singleton driver (like we have for unreliable-libc) so that we run both the normal I/O backend, and this one. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Introduces a new IO back-end which otherwise acts like MemoryIO, but yields on each call to force functions to be safely re-entrant. Will be used for turso-stress in Antithesis