What    |Removed                     |Added
                 CC|                            |

--- Comment #3 from 2012-10-17 16:42:44 PDT ---
(In reply to comment #2)
> > This is a big change in D, so before going this route I suggest to think 
> > well
> about this topic.
> The thing is that it _isn't_ memory safe. There's no question of that. So, per
> the definition of @safe, it has no business being @safe. It needs to be
> @system. If it's not, then SafeD is broken. I don't see how anyone could argue
> otherwise.
> ...

The code segment must be rejected, but what makes it unsafe is the escaping.
Banning the slicing is not very precise.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to