public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/42593] [c++0x] [4.5 Regression] std::bind not assignable to std::function
Date: Sun, 03 Jan 2010 18:07:00 -0000	[thread overview]
Message-ID: <20100103180703.17232.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42593-3237@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2010-01-03 18:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 12:37 [Bug libstdc++/42593] New: [c++0x] " d dot frey at gmx dot de
2010-01-03 12:47 ` [Bug libstdc++/42593] [c++0x] [4.5 Regression] " paolo dot carlini at oracle dot com
2010-01-03 14:13 ` redi at gcc dot gnu dot org
2010-01-03 14:26 ` paolo dot carlini at oracle dot com
2010-01-03 15:07 ` redi at gcc dot gnu dot org
2010-01-03 15:11 ` paolo dot carlini at oracle dot com
2010-01-03 16:03 ` paolo dot carlini at oracle dot com
2010-01-03 16:28 ` redi at gcc dot gnu dot org
2010-01-03 16:34 ` paolo dot carlini at oracle dot com
2010-01-03 17:57 ` redi at gcc dot gnu dot org
2010-01-03 18:05 ` paolo dot carlini at oracle dot com
2010-01-03 18:07 ` redi at gcc dot gnu dot org [this message]
2010-01-03 20:58 ` paolo dot carlini at oracle dot com
2010-01-03 21:03 ` paolo dot carlini at oracle dot com
2010-01-03 22:10 ` redi at gcc dot gnu dot org
2010-01-04 10:30 ` paolo dot carlini at oracle dot com
2010-01-10 13:46 ` paolo dot carlini at oracle dot com
2010-01-10 16:26 ` redi at gcc dot gnu dot org
2010-01-12  0:54 ` redi at gcc dot gnu dot org
2010-01-12  0:55 ` redi at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100103180703.17232.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).