From 9e8544d717379c6bee9325cc473ccd40c994bf73 Mon Sep 17 00:00:00 2001 From: Zac Hatfield-Dodds Date: Sat, 6 Aug 2022 22:48:05 -0700 Subject: [PATCH] Clarify docs on checkpoints in async iterables Closes #2388 --- docs/source/reference-core.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/reference-core.rst b/docs/source/reference-core.rst index 58d583a39d..e8d4bd6762 100644 --- a/docs/source/reference-core.rst +++ b/docs/source/reference-core.rst @@ -90,9 +90,9 @@ them. Here are the rules: exception, it might act as a checkpoint or might not.) * This includes async iterators: If you write ``async for ... in ``, then there will be at least one checkpoint before - each iteration of the loop and one checkpoint after the last - iteration. + trio object>``, then there will be at least one checkpoint in + each iteration of the loop, and it will still checkpoint if the + iterable is empty. * Partial exception for async context managers: Both the entry and exit of an ``async with`` block are