Slicing static arrays should be @system
Jakob Ovrum
jakobovrum at gmail.com
Sat Nov 3 23:17:55 PDT 2012
On Sunday, 4 November 2012 at 05:58:20 UTC, Jonathan M Davis
wrote:
> I think that anything that the compiler can't absolutely
> gurantee is @safe
> must be @system. If that's annoying in some places, then that's
> life, because
> we can't compromise on SafeD just because a few things that we
> use a lot can't
> be @safe. Now, if we can make further improvements that make it
> so that the
> compiler _can_ determine that something is actually @safe when
> before it
> couldn't, then that's great. So, in at least some cases,
> compiler improvements
> could be used to reduce the annoyance factor, but I don't think
> that we can
> compromise on this.
>
> - Jonathan M Davis
I completely agree, but I don't think we should decide what
should be guaranteed and what cannot by the current state of the
compiler. We need a properly specified goal that programmers can
rely on, and implementers work towards.
More information about the Digitalmars-d
mailing list