Paul Fultz II

> I don't believe this is a good use case. It seems more than the decorate function either doesn't do enough or you want it to do too much things....

There is merge conflict, so this cannot be merged.

Suppose you have a trait defined like this: ``` cpp TICK_TRAIT(is_incrementable) { template auto require(T&& x) -> valid< decltype(x++), decltype(++x) >; }; ``` Then the trait can be checked like...

> Which macro? The most obvious on TICK_REQUIRES traps at compile time. Which permits a function to be included/excluded from consideration for Overload depending on it's requirements? Yes that is...

> But what do I do if I DON'T want it to trap - I just want the the > overload to be considered only if the ++ operator is...

> Will invoke a error at compile time if the type Cont doesn't fulfill the requirements of Sortable. As I understand the documentation, the equivalent in TICK is: Its important...

> If C doesn't not fulfill the requirements of an Associative_container, one will get a compile time error. No, you get overload resolution failure, which turns into an error if...

> If T doesn't support the ++ operator we get a compilation error with a useful error message saying that the ++ operator is not supported. Thats not the error...

Thanks, are you able to add some tests?

Thanks. I've just added support for Visual Studio. However, this won't work for msvc, since msvc needs to use the `__LINE__` macro. I think I'll try to merge this in,...