From 1c9520020e84623f1db9348fdddab7686b81140f Mon Sep 17 00:00:00 2001 From: Kyle Marek-Spartz Date: Mon, 12 Jan 2015 17:27:35 -0600 Subject: [PATCH] unvalid > invalid --- doc/error-handling.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/error-handling.txt b/doc/error-handling.txt index 904cc34a..b65016b8 100644 --- a/doc/error-handling.txt +++ b/doc/error-handling.txt @@ -19,7 +19,7 @@ On the other hand, it might be nice to be able to resume here if the code that provided the string is far away and you don't want to have to manually propagate the error out. -Programmatic errors like unvalid argument types should halt the fiber but the +Programmatic errors like invalid argument types should halt the fiber but the programmer will not want to resume that at runtime. Using the mechanism here is fine since it would then dump a stack trace, etc. But it won't take advantage of resuming. @@ -76,5 +76,3 @@ Given those, I'm thinking: will run the fiber. If it fails with a programmatic error, the invoked fiber dies, but the parent does not. It gets the callstack and error as some sort of object it can poke at. - -