[Issue 14868] MmFile destructor seems to corrupt memory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14868

--- Comment #9 from Sergei Degtiarev <sdegtiarev at yahoo.com> ---
(In reply to Dmitry Olshansky from comment #8)
> Pull requests are welcome from anybody.
Ok, good, I can do this. However I'm barely three days on the forum and don't
know which way to go. I see at least three variants:
- straightforward, to throw out enforce, it will work safely, guarantee
- at C level, we can duplicate the file descriptor
- from designer's perspective, I'd simply remove this excess constructor
overload. Since we don't control lifetime of these two separate instances, File
and MmFile, they should not share same resource, file descriptor. But won't
this impact existing code? (if there is any)
Besides that, I can't code neither test it for systems other than POSIX ones.
Is it normal to live with two different implementations?

--