Bad array indexing is considered deadly

Joseph Rushton Wakeling via Digitalmars-d digitalmars-d at puremagic.com
Sun Jun 4 11:15:08 PDT 2017


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.

Incidentally, I wouldn't limit the area of concern here to array 
bound access issues.  This is more about the ability of _any_ 
error to propagate in applications of this nature, where you have 
many independent tasks being spawned in separate threads or (more 
often) fibers, and where you absolutely do not want an error in 
one task preventing you from being able to continue with others.


More information about the Digitalmars-d mailing list