blog

commit

4bdb38c08d33b27136bc217ef95dfd36d27fbb76

parent

eaeb3345f772b0d6cd481343546eaf5a3869de0a

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2026-07-13 12:28

async loops: typos

Diffstat

1 files changed, 2 insertions, 2 deletions

diff --git a/_content/posts/2026-04-19-more-async-loops/index.md b/_content/posts/2026-04-19-more-async-loops/index.md

@@ -1,5 +1,5 @@
    1     1 ---
    2    -1 title: Three more ways to think about asyncronous loop
   -1     2 title: Three more ways to think about asyncronous loops
    3     3 date: 2026-04-19
    4     4 tags: [code, async, python]
    5     5 description: I created a coroutine-only, unix-only, stateless alternative to asyncio.
@@ -56,7 +56,7 @@ is that all blocking I/O can be expressed as waiting for a *file descriptor* to
   56    56 be ready. After that, you can do different things with that file descriptor,
   57    57 for example reading a file or receiving from a socket.
   58    58 
   59    -1 Not every action on can be expressed this way though. The workaround in that
   -1    59 Not every action can be expressed this way though. The workaround in that
   60    60 case is to perform the action in a separate thread and then write to a self
   61    61 pipe. This has some overhead, but it allows to keep the loop itself simple.
   62    62