On 21 Sep 2013 at 19:58, Stephan T. Lavavej wrote:
[Niall Douglas]
You're right of course, but it's hard for me to work around VS2013's limitations here without being able to specialise a template for lambda types. Would you know Stephan how to do this on VS2013? I appreciate if it were easy you'd have already fixed the std::result_of<> shipped in the STL, but maybe it's easier than I am thinking?
I don't know how. My plan is to ask the compiler for targeted Expression SFINAE support when I get to implementing the SFINAE result_of rules.
Thanks for the quick answer. I discoved an answer to half of my problem: using unary + on a non-capturing lambda type erases the lambda-ness and produces its equivalent callable function pointer type, something easily specialised for and therefore filterable out to inhibit that overload for consideration. All that remains now is to figure out a way of specialising for capturing lambda types. Niall -- Currently unemployed and looking for work. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/