Subject: Re: [boost] [Boost-announce] [afio] Formal review of Boost.AFIO
From: Ahmed Charles (acharles_at_[hidden])
Date: 2015-09-01 03:39:22
I have received/noted these additional reviews:
Andreas Schafer <gentryx_at_[hidden]>
Antony Polukhin <antoshkka_at_[hidden]>
Giovanni Piero Deretta <gpderetta_at_[hidden]>
If you are still working on a review that you would like to be
considered, let me know. Otherwise, I'll be summarizing the results in a
On 8/31/2015 1:13 AM, Ahmed Charles wrote:
> I have reviews from the following people:
> Roland Bock <rbock_at_[hidden]>
> Paul A. Bristow <pbristow_at_[hidden]>
> Thomas Heller <thom.heller_at_[hidden]>
> Hartmut Kaiser <hartmut.kaiser_at_[hidden]>
> Jeremy Maitin-Shepard <jeremy_at_[hidden]>
> If you've sent a review and I've missed it, do let me know. There have
> been lots of emails this week and I want to make sure I've caught all of
> the reviews.
> On 8/22/2015 6:08 PM, Ahmed Charles wrote:
>> The formal review of the Boost.AFIO library starts, August 21st and ends
>> on Monday August 31st.
>> Boost.AFIO provides a portable API implementing synchronous and
>> asynchronous race-free filesystem and scatter-gather file i/o. It requires
>> a minimum of C++ 11. It has minimum dependencies on a Filesystem TS and a
>> Networking TS implementation (e.g. Boost.Filesystem and Boost.ASIO).
>> Backends are provided for the Windows NT kernel and POSIX.
>> The utility of a portable library providing strong concurrent race
>> guarantees about filesystem and file i/o can be seen in its tutorial where
>> a transactional ACID key-value store is built from first principles.
>> Boost.AFIO was brought to Boost as part of GSoC 2013 and Niall Douglas has
>> continued to develop and improve the library since then, generating two
>> internal implementation libraries Boost.APIBind and Boost.Monad which are
>> expected to be separately brought for Boost review in 2016.
>> The documentation can be found here:
>> The source code can be found here:
>> Online web compiler playpen can be found here:
>> Please answer the following questions:
>> 1. Should Boost.AFIO be accepted into Boost? Please state all
>> conditions for acceptance explicity.
>> 2. What is your evaluation of the design?
>> 3. What is your evaluation of the implementation?
>> 4. What is your evaluation of the documentation?
>> 5. What is your evaluation of the potential usefulness of the library?
>> 6. Did you try to use the library? With what compiler? Did you have
>> any problems?
>> 7. How much effort did you put into your evaluation? A glance? A quick
>> reading? In-depth study?
>> 8. Are you knowledgeable about the problem domain?
>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-announce
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk