On Wed, Jun 29, 2016 at 10:12 PM, Barrett Adair
(snip)
Since I haven't received a response to my last post, I decided to go
ahead and start moving the CallableTraits code into a Boost.TypeTraits fork today [1].
First, I'll get my most important questions out of the way (feel free to
respond to only this paragraph). Before I reformat my reference documentation to match that of TypeTraits, I would like to know whether this would be a fruitful endeavor. Are any of the features added in this fork worth keeping in Boost.TypeTraits? If so, which features (if any) need to be removed, renamed, or re-designed? All of the features documented in my non-Boost reference documentation [2] are present in this fork, albeit in a Boost-ified form (e.g. `std::integral_constant` is now `boost::integral_constant`).
(snip)
[1] https://github.com/badair/type_traits/tree/feature/callable_traits [2]
http://badair.github.io/callable_traits/doc/html/callable_traits/reference.h... For clarification, I would like to emphasize the fact that my code IS actually integrated into the TypeTraits fork -- my previous message seems to suggest otherwise. All my test cases pass with GCC 6.1, and Visual Studio 2015 passes all test cases that don't rely on the constexpr-ness `boost::integral_constant::operator bool`. The 9 that fail will need to be updated. I have not built the fork's test suite on other compilers yet. Barrett