Hi thanks for raising this, as far as single machine computation is concerned, Concurnas supports unchecked exceptions. Also, exceptions occurring within the context of isolates are either handled by a (overridable) error handler (which defaults to output to stderr) or more commonly, set to the returned ref from the isolate execution. Then when that ref is accessed the exception is then thrown by the accessor(s) and can be handled as appropriate.

As far as distributed computing is concerned, here the error landscape is much larger than with single machine computation (network disconnections etc). The distributed computing component of Concurnas allows one to define custom error handlers which can deal with errors occurring specifically from distributed computing, and there are a couple of pre-defined error handlers which can be used to assist here (fail on first incident and retry up to x times): https://concurnas.com/docs/distComp.html#common-error-handli...

The documentation about distributed computing (and distributed error handling in particular) could be better written. I will look to make that a priority now that you've raised this point.

That sounds great. Thanks!