On Monday, 9 November 2015 at 08:53:30 UTC, Iain Buclaw wrote:
Instead of funneling blame, this could be resolved in the move to 2.067(maybe just skipping to 2.068). The complete
The warning still appears in dmd 2.069. Do you recommend filing a bug with dmd?
