On Sunday, 4 June 2017 at 19:12:42 UTC, Jacob Carlborg wrote:
On 2017-06-04 20:15, Joseph Rushton Wakeling wrote:
On Friday, 2 June 2017 at 15:19:29 UTC, Andrei Alexandrescu
wrote:
Array bound accesses should be easy to intercept and have
them just
kill the current thread.
Ideally, fiber, as well. Probably the real ideal for this
sort of
problem is to be able to be as close as possible to Erlang,
where errors
bring down the particular task in progress, but not the
application that
spawned the task.
Erlang has the philosophy of share nothing between processes
(green processes), or task as you call it here. All allocations
are process local, that makes it easier to know that a failing
process doesn't affect any other process.
If I'm not wrong, it also uses a VM, also if there's the
availability of a native code compiler...
If a VM is involved, it's another game...
/Paolo
