Bug 13911 – rename std.stdio to std.io

This was proposed in the dlang.org documentation comments [1][2] by Oleg Bt. Why "std.stdio"? May be better "std.io"? And "std.stdio.stderr" looks bad. I think it's a good point, there isn't any benefit in using the C-ish stdio name. And because std.stdio is one of the most used modules, it would even save some typing. [1]: http://dlang.org/library/std/stdio.html [2]: https://disqus.com/home/discussions/vibe-d/module_stdstdio_d_programming_language_digital_mars

Please don't! This is the future planned home of the new io system I am working on. If it's all the same, can we hold off on this? I ask for mercy, since I have not been exactly speedy in getting this improvement finished, if others think it's not worth waiting for, then so be it. Note that I will take Walter's "don't change things for the sake of changing them" stance on this, although I admit somewhat for ulterior motives :) This will break just about every piece of code out there...

Is there any problems with « deprecated » ? Just make stdio marked deprecated so it will show a warning. And make a « public import std.io; ». We should rename stdio to io i think. If you work on « new » io - you'll just add your functionality to « old » io : is there any problems ?

We can do that later. I just don't want to do std.io2, especially after renaming std.stdio. My system looks nothing like std.stdio, it will be a very different interface, with backwards-compatible access via std.stdio.

> And because std.stdio is one of the most used modules, it would even save some typing. I think it would create a lot of typing as hundreds of imports and other written material need to be updated, and the habit of typing stdio for existing users needs to be broken. I'm very strongly against this change, it would even cause years of hassle in comments as people call it proof that D is excessively unstable.... and for exactly zero benefit. If std.io is a new module, that's ok, then std.stdio can be relabeled as a compatibility module (with D code and with C) with a note to the new one while still staying there and NOT being deprecated - extremely important that it stay there, so code isn't broken. I think Steven's plan is a good one, and this bug ought to be closed as WONT FIX.

i'm infamous for my "cosmetic issues are important" ranting, but this time i think that it's not worth it.

Marking as won't fix as several people have asked for, and since Martin never made a case for keeping this open.