This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/42593] [c++0x] [4.5 Regression] std::bind not assignable to std::function
- From: "redi at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Jan 2010 18:07:03 -0000
- Subject: [Bug libstdc++/42593] [c++0x] [4.5 Regression] std::bind not assignable to std::function
- References: <bug-42593-3237@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #10 from redi at gcc dot gnu dot org 2010-01-03 18:07 -------
OK
P.S.
(In reply to comment #8)
>
> (the ability to use this workaround was the main reason I fixed std::bind<void>
> recently)
I think I've mentioned to Paolo in private mail that we could use bind<R>
(specifically, bind<void>) in several places because doing so should reduce
compile time, as it avoids using result_of and decltype to determine the return
type. I haven't done so yet, because deducing the return type provides better
testcases for std::bind while I'm still working on it. Once the work is
complete, we should consider using bind<R> in <mutex> and <future>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42593