From c911dc4ac89d07ec2af44fd8e30c6ceb5562ab47 Mon Sep 17 00:00:00 2001
From: JJ
Date: Tue, 11 Jul 2023 21:32:29 -0700
Subject: move docs into docs folder and update the readme

---
 ASYNC.md | 17 -----------------
 1 file changed, 17 deletions(-)
 delete mode 100644 ASYNC.md

(limited to 'ASYNC.md')

diff --git a/ASYNC.md b/ASYNC.md
deleted file mode 100644
index 5b9fa7e..0000000
--- a/ASYNC.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# Asynchronous Programming
-
-I don't know enough about asynchronous programming to get started with this section.
-
-Existing systems to learn from:
-- https://github.com/status-im/nim-chronos
-- https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/
-- https://tokio.rs/tokio/tutorial
-- https://morestina.net/blog/1686/rust-async-is-colored
-- https://ziglearn.org/chapter-5/
-- https://kristoff.it/blog/zig-colorblind-async-await/
-- https://en.wikipedia.org/wiki/Async/await
-- https://old.reddit.com/r/elixir/np688d/
-
-Asynchronous programming is hard to design and hard to use. Even Rust doesn't do a great job. It *shouldn't* need built-in language support - we should be able to encode it as a type and provide any special syntax via macros. Note that async is not just threading! threading is solved well by Rust's rayon and Go's (blugh) goroutines.
-
-Is async worth having separate from effects?
-- 
cgit v1.2.3-70-g09d2