On Thursday, 22 August 2013 at 15:50:50 UTC, John Colvin wrote:
On Thursday, 22 August 2013 at 15:42:15 UTC, Ramon wrote:
One (OK, not very creative) example that comes to mind is to
have less experienced programmers to work in "safe mode" only,
which anyway is good enough for pretty everything the average
app needs, and to limit "system mode" to seasoned programmers.
If I was managing a D based team, I would definitely make use
of safe/system for code reviews. Any commit that touches
@system code* would have to go through an extra stage or
something to that effect.
Yep. Considering that pretty every non-trivial/small utility
software is layered anyway it comes even quite natural.
But I (often involved in systems stuff) will also use it as a
private warning system. Trying to get done whatever can get done
using @safe. Quite probably ("probably" because I lack experience
with D) it will even reflect back on the design along the line of
tinkering "does this *really* need to be here?".
