On Sun, 24 Jan 2016 21:37:40 -0500, Andrei Alexandrescu wrote:
> Hot off the press! http://wiki.dlang.org/Vision/2016H1 -- Andrei
I'm not fond of the militaristic terminology for participants. Novice,
adept, master, maybe?
The section on safety is pretty short. I'd like to see in it:
* Guidelines for what should be made @trusted in Phobos (should we trust
Win/Posix API functions? should we only trust wrappers that take D arrays
rather than pointers? can we, for instance, create a @trusted wrapper
* Efficiency / safety tradeoff guidelines (should Phobos provide a
slightly faster implementations of things that aren't @safe? In those
cases, should it provide both @safe and fast alternatives?)
* @safe / @trusted IO as a goal
As is, there are a smattering of things in Phobos that aren't @safe but
seem like they could or should be, with no explanation and no safe
alternatives. I think almost all IO is @system. This makes it hard and
sometimes confusing to try to write @safe code.