On 5/26/20 12:31 PM, Bruce Carneal wrote:
Currently a machine checked @safe function calling an unannotated extern C routine will error out during compilation. This is great as the C routine was not machine checked, and generally can not be checked. Post 1028, IIUC, the compilation will go through without complaint. This seems quite clear. What am I missing?
If that's the case, it's the death of DIP 1028.
