Meson/wren
1
0
Fork 0
forked from Mirror/wren
Code Pull Requests Activity

unvalid > invalid

Browse Source
This commit is contained in:
Kyle Marek-Spartz
2015-01-12 17:27:35 -06:00
parent 12b8168b94
commit 1c9520020e
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/error-handling.txt
View File

@ -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 provided the string is far away and you don't want to have to manually propagate
the error out. 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 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 fine since it would then dump a stack trace, etc. But it won't take advantage
of resuming. 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 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 dies, but the parent does not. It gets the callstack and error as some sort
of object it can poke at. of object it can poke at.