On Wed, Sep 2, 2015 at 12:37 PM, Dmitry Olshansky via
Digitalmars-d-announce <email@example.com> wrote:
> Because the compiler and library releases go in lockstep we'd have to wait
> for another release cycle to even field-test @nogc. Not acceptable really.
> Phobos ends up battle testing every new feature and if it wasn't new
> features will be definitely shipped in a broken state. Let's not forget
> that new D frontend features still have many bugs that stay undetected even
> after testing in Phobos.
> Dmitry Olshansky
Surely the compiler should always rely on the previous compiler + standard
Is there really a valid reason not to do this? Surely if the dog food is so
bad no one should be eating?