On Friday, August 12, 2011 10:48 Jimmy Cao wrote: > On Fri, Aug 12, 2011 at 7:53 AM, dsimcha <dsim...@yahoo.com> wrote: > > On 8/10/2011 9:22 AM, dsimcha wrote: > >> The review of the new std.path is drawing to a close and it looks like > >> another success! (Congratulations, Lars.) Lately, though, the queue of > >> stuff to review has been getting rather long, admittedly a problem we'd > >> like to have. I want to get a list of stuff that's ready or will be > >> ready in short order, so we can prioritize. > >> > >> I know at least the following are ready or fairly close. Please list > >> anything else: > >> > >> std.regionallocator (A segmented stack memory allocator, by me. I'd like > >> to fast-track this because it's being used in the GSoC project I'm > >> mentoring and getting it into Phobos would simplify things for us.) > >> > >> std.parallelalgorithm (A small module of parallel implementations of > >> various algorithms, by me. This one can wait because it's pretty niche > >> and nothing I know of depends on it.) > >> > >> std.process (New and much improved, by Steve Schveighoffer and IIRC Lars > >> Kylingstad also contributed. Personally I'd like this to be given a high > >> priority b/c the old std.process sucks so much and it's been waiting so > >> long for compiler bugs to get fixed, etc.) > >> > >> std.log (Logging module by Jose Armando Garcia.) > >> > >> curl wrapper (By Jonas Drewsen.) > >> > >> std.variant (Major improvements, by Robert Jacques.) > > > > Ok, so in addition to the above, we also have Jesse Phillips's CSV > > parser. > > > > The review for std.path has been successfully completed, so let's get > > > > another iron in the fire. > > > > As far as stuff that's completely ready to go (no caveats, need for > > polishing, etc.), I know std.regionallocator and the curl wrapper are. If > > there's anything else, please speak up. I'm willing to postpone > > std.regionallocator if the curl wrapper is ready to be reviewed right > > now, since I think the curl wrapper is more universally useful. > > Therefore, IMHO next in line should be the curl wrapper. > > That's reasonable. I also think that the Curl wrapper should be reviewed > next.
std.log has been in the review queue the longest, so I would say that that should be next except that when I posted a question about it a couple of days ago, he never responded. So, we should probably just review the curl wrapper next and get on with it. - Jonathan M Davis