On Tuesday, 17 June 2014 at 20:25:52 UTC, Walter Bright wrote:
You have a lot of good thoughts on this issue.
You have specific problems in mind but do not identify them
other than in vague terms. I guarantee that I am really, really
bad at mindreading.
Instead, I would strongly prefer that you:
1. write bugzilla issues for the problems that you identify
2. connect those bugzilla issues regarding @safe with the
'safe' keyword
3. construct specific proposals for how to fix these issues.
The proposals don't actually have to be pull requests, just
descriptions on the bugzilla pages for how to fix.
4. write pull requests for the documentation
Even doing just one of 1..4 would be most appreciated. Merely
asserting that @safe is broken/buggy/etc. will not result in
progress.
I don't think he will. He's been explaining you for the past
several posts that this process is fundamentally broken, and
won't achieve the goals of @safe.
Please have a step back and look at the broader issue here.
