public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dangelog at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107525] propagate_const should not be using SFINAE on its conversion operators
Date: Fri, 04 Nov 2022 15:58:28 +0000	[thread overview]
Message-ID: <bug-107525-4-oDv9tXfLLn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107525-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525

--- Comment #9 from Giuseppe D'Angelo <dangelog at gmail dot com> ---
(In reply to Jonathan Wakely from comment #5) 
> Please don't! At least not in the next 9 days. We intend to vote out LFTSv3
> at next week's meeting, there will be no more proposals for LFTS considered.
> And I don't want to derail the vote next week by having open proposals
> arriving at the last minute.

No problem, I wouldn't have done this before a few weeks anyhow.


> Feel free to file a library issue though. If propagate_const ever gets
> proposed for inclusion in the standard then this should be taken into
> account.

OK.

Thank you very much for the prompt fix.

(Ville: guess what, this bug stem from trying to make uic and friends use
propagate_const. Small world!)

  parent reply	other threads:[~2022-11-04 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 11:38 [Bug libstdc++/107525] New: " dangelog at gmail dot com
2022-11-04 13:59 ` [Bug libstdc++/107525] " redi at gcc dot gnu.org
2022-11-04 14:07 ` redi at gcc dot gnu.org
2022-11-04 14:26 ` redi at gcc dot gnu.org
2022-11-04 14:43 ` dangelog at gmail dot com
2022-11-04 15:04 ` redi at gcc dot gnu.org
2022-11-04 15:09 ` redi at gcc dot gnu.org
2022-11-04 15:10 ` redi at gcc dot gnu.org
2022-11-04 15:15 ` ville.voutilainen at gmail dot com
2022-11-04 15:58 ` dangelog at gmail dot com [this message]
2022-11-05 14:01 ` cvs-commit at gcc dot gnu.org
2022-11-05 14:04 ` redi at gcc dot gnu.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=bug-107525-4-oDv9tXfLLn@http.gcc.gnu.org/bugzilla/ \
    --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).