When data get mangled there can be significant security issues as well.. Just saying if you get bounds checks with great safety thats preferable to me to perfect safety in 1 part with bound checks since you need to get the concurrency correct in the app and if you do then the language / runtime is irrelevant .
Ben On Fri, Aug 2, 2013 at 1:20 AM, Jonathan S. Shapiro <s...@eros-os.org>wrote: > Data getting mutilated to the wrong values is quite different from a > failure of memory safety. The security model, for example, relies on memory > safety. > > Memory safety that is only safe if you do the right locking isn't memory > safety. > > >
_______________________________________________ bitc-dev mailing list bitc-dev@coyotos.org http://www.coyotos.org/mailman/listinfo/bitc-dev
