From d38699324eed9ee91a8b7baca93aba961067a46e Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Mon, 7 Mar 2016 20:51:40 -0800 Subject: 2732 --- Readme.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 4a32fc07..d5138a45 100644 --- a/Readme.md +++ b/Readme.md @@ -103,7 +103,7 @@ mind. The nice experience for an outsider would be to just change that line and see if any tests fail. This is only possible if we eliminate all manual QA from our release process. -*So…* +*Therefore…* In Mu, it will be possible for any aspect of any program that you can manually test to also be turned into a reproducible automatic test. This may seem like @@ -181,6 +181,15 @@ help, as I've described above. Another thing that helps is a zoomable interface to the *trace* of operations performed in the course of a test (More details: http://akkartik.name/post/tracing-tests) +High-level languages provide three things: + +a) Expressiveness (nested expressions, function calls, etc.) +b) Safety (type checking, warnings, etc.) +c) Automation (garbage collection, a scheduler for green threads, etc.) + +Mu ignores a) for a time, but there's no reason it can't provide b) and c), as +you'll see below. + *Taking Mu for a spin* Mu is currently implemented in C++ and requires a unix-like environment. It's -- cgit 1.4.1-2-gfad0