This also runs against my desire to keep the top level, first class
part of the API as small as possible, and having each entry fan out
as needed.  I'm making the assumption that most raised errors will
be non-continuable; if correct, this is as simple as I can make it
for those writing code that uses SRFI 198.

- Harold

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

The current draft has:

(raise-foreign-error alist [continuable?])

RnRS has `raise` and `raise-continuable` separately. Should we match
that naming convention and split it into two different procedures?

(raise-foreign-error alist)
(raise-continuable-foreign-error alist)