[boost] [Fit] formal review ends today, 13th March.

Subject: [boost] [Fit] formal review ends today, 13th March.
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2016-03-13 09:32:31

Hi,

The formal review of Paul Fultz II's Fit library ends today, 13th March. 
If you had not time to do the review and you plan to do it, please let 
us know so that we see if the review can be extended.

Up to now we had 3 formal review (2 for conditional acceptance and 1 
against, not now).
I have not done a review myself, but I have created a lot of issues on 
Github.

Best regards,
Vicente

Fit is a header-only C++11/C++14 library that provides utilities for 
functions and function objects.

Fit is:

- Modern: Fit takes advantages of modern C++11/C++14 features. It 
support both `constexpr` initialization and `constexpr` evaluation of 
functions. It takes advantage of type deduction, varidiac templates, and 
perfect forwarding to provide a simple and modern interface.

- Relevant: Fit provides utilities for functions and does not try to 
implement a functional language in C++. As such, Fit solves many 
problems relevant to C++ programmers, including initialization of 
function objects and lambdas, overloading with ordering, improved return 
type deduction, and much more.

- Lightweight: Fit builds simple lightweight abstraction on top of 
function objects. It does not require subscribing to an entire 
framework. Just use the parts you need.

Fit is divided into three components:

* Function Adaptors and Decorators: These enhance functions with 
additional capability.

* Functions: These return functions that achieve a specific purpose.

* Utilities: These are general utilities that are useful when defining 
or using functions

Fit has been tested on gcc 4.6-4.9, clang 3.4-3.7, and Visual Studio 2015.

For more information see:

Github:https://github.com/pfultz2/Fit/tree/boost

Documentation:http://pfultz2.github.io/Fit/doc/html/

We encourage your participation in this review. At a minimum, kindly state:
- Whether you believe the library should be accepted into Boost
   * Conditions for acceptance
- Your name
- Your knowledge of the problem domain.

You are strongly encouraged to also provide additional information:
- What is your evaluation of the library's:
   * Design
   * Implementation
   * Documentation
   * Tests
   * Usefulness
- Did you attempt to use the library? If so:
   * Which compiler(s)
   * What was the experience? Any problems?
- How much effort did you put into your evaluation of the review?

More information about the review process can be found 
here:http://www.boost.org/community/reviews.html

We await your feedback!