From 5f21f71731b7923f60d6d3b134137ce819b60134 Mon Sep 17 00:00:00 2001
From: Julian Hofer <julianhofer@gnome.org>
Date: Sun, 22 Oct 2023 13:20:46 +0200
Subject: [PATCH] book: Start with conclusion

---
 book/src/main_event_loop.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/book/src/main_event_loop.md b/book/src/main_event_loop.md
index 0da2aa123a9e..00f466b03c89 100644
--- a/book/src/main_event_loop.md
+++ b/book/src/main_event_loop.md
@@ -249,5 +249,11 @@ Filename: <a class=file-link href="https://github.com/gtk-rs/gtk4-rs/blob/master
 
 
 So when should you spawn an `async` block and when should you spawn a thread?
-- If you have `async` functions for your IO-bound operations at your disposal, feel free to spawn them on the main loop.
-- If your operation is computation-bound or there is no `async` function available, you have to spawn threads.
+
+# TODO
+
+- computation bound -> threads + channels
+- IO:
+    - if you have glib/smol/async-std functions -> spawn on main loop (+ maybe channels)
+    - if tokio lib is better -> spawn on tokio + channels
+    - if those are not good options -> threads + channels