Jason House wrote: > I'm a bit annoyed that issue 1719 [1] got closed with a claim that d 1.026 > and d 2.010 fixed the problem. 2.011 will put it back and fix it properly.