On Tuesday, 22 April 2014 at 09:02:21 UTC, Walter Bright wrote:
On 4/22/2014 12:11 AM, Jacob Carlborg wrote:
On 22/04/14 01:02, Walter Bright wrote:
The thing is, with iOS ARC, it cannot be statically
guaranteed to be
memory safe. This makes it simply not acceptable for D in the
general
case. It "works" with iOS because iOS allows all kinds of
(unsafe) ways
to escape it, and it must offer those ways because it is not
performant.
So does D. That's why there is @safe, @trusted and @system.
What is the unsafe
part of ARC anyway?
As I said, it is when it is bypassed for performance reasons.
A system that is automatically safe but can be manually managed
for extra performance. That sounds very D-ish.