about summary refs log tree commit diff stats
path: root/Readme.md
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-01-02 15:27:48 -0800
committerKartik K. Agaram <vc@akkartik.com>2015-01-02 15:27:48 -0800
commit5860b6614bdb3cb7d1d4626cc4b3b46f6b4e9849 (patch)
treeb9d10392e67ecf394984d95bfa926e402c9f1e3b /Readme.md
parent4ccca667454d268c66b34d0d2b13ec8f2b36c293 (diff)
downloadmu-5860b6614bdb3cb7d1d4626cc4b3b46f6b4e9849.tar.gz
491
Diffstat (limited to 'Readme.md')
-rw-r--r--Readme.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/Readme.md b/Readme.md
index 15580d5e..a036ff46 100644
--- a/Readme.md
+++ b/Readme.md
@@ -207,6 +207,8 @@ Yet another example forks two 'routines' that communicate over a channel:
 
   # The exact order above might shift over time, but you'll never see a number
   # consumed before it's produced.
+
+  error - deadlock detected
 ```
 
 Channels are the unit of synchronization in mu. Blocking on channels are the
@@ -220,6 +222,9 @@ random memory locations. Bounds checking is baked deeply into the semantics,
 and pointer arithmetic will be mostly forbidden (except inside the memory
 allocator and a few other places).
 
+Notice also the error at the end. Mu can detect deadlock when running tests:
+routines waiting on channels that nobody will ever write to.
+
 ---
 
 Try running the tests: