In addition to those problems... Someone already pointed out in your other thread today that the current behavior of write! is documented and used by existing code that we cannot simply break.
Also, "the current API requires an explicit import" or "I want to give a method the same name without conflicts" are not really strong motivations for breaking stability, or for major architectural changes to the implementation.
We have talked to you many, many times about what types of proposals are useful and actionable here. We have told you very explicitly what you should be considering before making such feature requests. Please consider this a final warning.