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:
https://boostgsoc13.github.io/boost.afio/doc/html/afio.html
The source code can be found here:
https://github.com/BoostGSoC13/boost.afio/tree/boost-peer-review
Online web compiler playpen can be found here:
http://melpon.org/wandbox/permlink/DR8wCpu5Rl20GMdM?
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?
