On 30/05/14 12:53, w0rp wrote:
It's always, always easier to experiment by releasing a dub package.
Including a module in the standard library requires the approval of a
commity. You can always release a dub package, no one is going to stop you.
std.experimental is probably best used for things that are 90% of the
way into being included in std. We could find out how to address the
remaining 10% then by seeing how people actually use the modules.
I agree. In my opinion std.experimental would be for modules that have
already passed the standard review process and are put in
std.experimental for a couple of releases to battle test the API's.
--
/Jacob Carlborg
