From: joel falcou (joel.falcou_at_[hidden])
Date: 2008-08-11 02:57:08
> I would say don't. It's not friendly to generic code and it sounds
like
> "or constraints" which were left out of C++0x for
very good reasons. If
> you could be more specific about what
you're trying to do I might be able
> to help find a better
solution. My first guess is that the answer will be
> found in
the use of traits.
Basically I want to make a concept which
represents class that supports the result_of protocol, ie exposes either a
result_type or a result inner class. So my first idea was to see if a
given type have either of this inner elements.