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. On Wed, Jul 31, 2013 at 11:20 PM, Bennie Kloosteman <[email protected]>wrote: > I agree with David here,,,i think this is an element that has not worked > .. What is the point of providing these safety gaurantees ( which has a > cost eg bounds checking) when you data gets mutilated and your app goes > foobar if you dont do the right things anyway ... >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
