On 7/11/2016 5:15 PM, deadalnix wrote:
On Monday, 11 July 2016 at 21:52:36 UTC, Walter Bright wrote:
The root problem is that "@safe guarantee memory safety and if it
doesn't it is a bug" provides no information as to what is the bug here
and no actionable items as to how to fix it, or even as to what needs
fixing.
It's kind of a meaningless criticism. Any piece of code has a bug if
it doesn't meet the specification, and there's no way to verify it
meets the specification short of proofs, and if anyone wants to work
on proofs I'm all for it.
In the meantime, please post all holes found to bugzilla and tag them
with the 'safe' keyword.
You know, there is a saying: "When the wise point at the moon, the idiot
look at the finger". I can't force you to look at the moon, I can only
point at it.
I don't see anything actionable in your comment.
