From d04d6d0d9fd3df615aef2b008f7f7c79afa55e54 Mon Sep 17 00:00:00 2001 From: Jim Pryor Date: Tue, 30 Nov 2010 23:54:28 -0500 Subject: [PATCH] coroutines tweak Signed-off-by: Jim Pryor --- coroutines_and_aborts.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/coroutines_and_aborts.mdwn b/coroutines_and_aborts.mdwn index 3d58e31e..32830795 100644 --- a/coroutines_and_aborts.mdwn +++ b/coroutines_and_aborts.mdwn @@ -358,7 +358,7 @@ How about this: Remind you of anything we discussed earlier? /Trivia. -Of course, it's possible to handle errors in other ways too. There's no reason why the implementation of `List.nth` *had* to raise an exception. They might instead have returned `Some a` when the list had an nth member `a`, and `None` when it does not. But it's pedagogically useful for us to think about this pattern now. +Of course, it's possible to handle errors in other ways too. There's no reason why the implementation of `List.nth` *had* to raise an exception. They might instead have returned `Some a` when the list had an nth member `a`, and `None` when it does not. But it's pedagogically useful for us to think about the exception-raising pattern now. When an exception is raised, it percolates up through the code that called it, until it finds a surrounding `try ... with ...` that matches it. That might not be the first `try ... with ...` that it encounters. For example: -- 2.11.0