This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [v3] Simplify a tad _Bind<_Functor(_Bound_args...)>


On 01/16/2010 01:12 AM, Jonathan Wakely wrote:
> N.B. another variation I tried (but didn't use, as it seemed to have
> no clear benefit) was to "un-overload" call() so that:
>
> operator()(...) uses call(...)
> operator()(...) const uses call_c(...) const
> operator()(...) volatile uses call_v(...) volatile
> and operator()(...) const volatile uses call_cv(...) const volatile
>
> This would mean that once overload resolution has decided which
> operator() to use, it doesn't then have to decide which call() member
> to use, because (IIRC) the second overload resolution goes through the
> same instantiations and argument deductions as the first overload
> resolution, which I think is unnecessary.
>   
Right. Today I had the same idea. Really, seems a waste of compiler
resources having overloading again when all it's decided anyway... We'll
see.

Paolo.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]