Have not worked with raise-continuable so I didn't realize that
distinction.  This point is all I need to justify that change
to the API, radically different behaviors deserve more separation
than an optional argument.  Thanks!

- Harold

----- Original message -----
From: Lassi Kortela <xxxxxx@lassi.io>
Date: Monday, July 27, 2020 7:33 AM

> raise and raise-continuable are fundamentally different procedures.
> The former is a continuation procedure that does not return. The
> latter is an ordinary procedure.
>
> From that pure point of view, it does not make much sense to conflate
> them into one.

Thanks for pointing this out. IMHO that settles the debate in favor of
separating `raise-foreign-error` and `raise-continuable-foreign-error`,
unless Harold wants to make further arguments for keeping them together.