On 6/13/2019 1:24 AM, Nicholas Wilson wrote: > No: the spec disagrees with the implementation, therefore at least one of them > is wrong. It does not immediately follow that it is the spec that is in error. @safe has always been about memory safety. The spec is wrong.