From 5860b6614bdb3cb7d1d4626cc4b3b46f6b4e9849 Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Fri, 2 Jan 2015 15:27:48 -0800 Subject: 491 --- Readme.md | 5 +++++ 1 file changed, 5 insertions(+) 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: -- cgit 1.4.1-2-gfad0