6: async checkpoints #16
Merged
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
jakkdl
force-pushed
the
6_async_checkpoints
branch
from
065404d to
6ad9d96
Compare
|
rebased onto master, fixed your comments, fixed TRIO103 errors in the 107_108 file, and incremented version~ ✨ |
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.
I had an eye on this one when working on trio103/104, which is why that one is a bit overkill for a relatively simple check - but made it a breeze to implement this one since it's got a large overlap.
Added messages temporarily as 300 & 301 to avoid numbering conflicts, will change that to 1XX once ready to merge. (Unfortunately needs changing in a bunch of places in the code)