Phobos.testing

dsimcha dsimcha at yahoo.com
Sat Oct 10 16:01:35 PDT 2009


I've noticed that it's somewhat difficult to get code into Phobos.  This is
somewhat understandable--noone wants a standard library full of buggy code
that noone understands.  On the other hand, it doesn't seem like there's a
very well-organized process for getting stuff into Phobos if you're not a main
contributor.

Should something like a Phobos.testing lib be created?  Such a project would
be an area of dsource.  The bar for getting stuff checked into here would be
relatively low.  If you write a module and check it into phobos.testing, it
indicates that you believe that it would be generally useful enough to go into
Phobos and are posting it for review/comment/other people to use with the
caveat that it might not be well tested yet.  This dsource project would use
its own forums to comment on the code and debate about what does and doesn't
belong in Phobos.  Every release, Andrei would pick off the best well-tested,
well-reviewed community-created feature and add it to the "real" phobos.

Overall, the point is that there should be a well-defined process for getting
code into Phobos and a well-defined place to post this code and comment on it.
 Bugzilla probably doesn't cut it because it's not easy to download, compile
and test lots of different snippets of code from here.



More information about the Digitalmars-d mailing list