On Wednesday, 1 February 2017 at 21:31:33 UTC, Walter Bright
wrote:
What part of the signature guarantees non-overlap?
At the rate D is going, pretty soon the entire function body will
be retold in the signature. What's the point when it is obvious
that in practice, we can actually analyze the content and get
BETTER coverage anyway?
(actually in the real world, it won't since nobody will care
enough to write `pure public return const(T) hi(return scope T t)
nothrow @nogc @safe @noincompetence @a_million_other_things {
return t; }`)
