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

[Paolo Carlini]

Hi,
> It passes all my tests so far: if Jason can fix the damn serious issue
> with class types, I think we should apply it.
>
> If everything goes well, I also have in my tree: some trivial changes to
> the overloads for volatile / const volatile which allow to enable the
> code (just use consistently volatile and const volatile also when
> passing around tuple<_Args...>); trivial changes int -> size_t in
> various places indexing std::tuple (this changed since TR1), then a
> check __i >= can also be removed, of course.
>
> .... and we should add a *ton* of testcases.
>   
So... for now I'm applying this incremental improvement, without
attempting anything special for the volatile / const volatile issue (at
some point I add an hack which passes the testsuite, but I didn't trust
it, treated differently those overloads in an ad-hoc way). Besides what
we discussed already, I also noticed inconsistencies in the way
temporary tuple<_Args...> were passed around, and decided to uniform
everything to use rvalue refs, which seems the right thing to do. If you
are aware of testcases that breaks because of that, more than welcome of
course...

Tested x86_64-linux, committed to mainline.

Paolo.

/////////////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CL_bind
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20100117/2738aaaa/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_bind
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20100117/2738aaaa/attachment-0001.ksh>