Barrett Adair

@eldiener See all the features starting with `has_*` and `is_*` [here](https://www.boost.org/doc/libs/develop/libs/callable_traits/doc/html/index.html). Not provided are features that already exist in C++11, listed below: * [is_function](https://en.cppreference.com/w/cpp/types/is_function) * [is_member_object_pointer](https://en.cppreference.com/w/cpp/types/is_member_object_pointer) * [is_member_function_pointer](https://en.cppreference.com/w/cpp/types/is_member_function_pointer) * [is_member_pointer](https://en.cppreference.com/w/cpp/types/is_member_pointer)...

Is it useful at all? Should it be split into multiple traits, or removed entirely? What was the rationale for the current design?

> Which one should it show? Should it stop showing the blue point when you're out of range? Yes, I would think so. I think ideally the X axis value...

Thanks for reporting. That's an interesting case I haven't seen before -- looks like it works correctly on GCC and Clang? Unfortunately, I don't have the bandwidth to dig into...

Let me know whenever you're ready for the PR. I'll use the macros you mentioned and add test cases/documentation. P.S. Congratulations on surviving the review process. I hope Fit makes...

@ldionne They do grant licenses for FOSS development upon request, but the latest version is likely not anywhere close to compiling the Hana test suite. I also doubt that there...

> I see two solutions: ... Perhaps there is a third (still far from ideal): What if we allow the client to pass a reference_wrapper-like template as a template template...

Edit: I just realized there is an open PR for this. I'll check it out later (I'm on mobile so I can't easily edit my above comment).

What are your thoughts on wrapping `` dependent code with an `#ifdef`, for those who cannot or wish not to include ``?

Did you compile with optimizations enabled, e.g. `-O3`? Hana is fast when I compile this code with optimizations enabled.