public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Daniel Krügler" <daniel.kruegler@gmail.com>
To: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Implement LWG 2686, hash<error_condition>
Date: Tue, 21 Mar 2017 21:26:00 -0000	[thread overview]
Message-ID: <CAGNvRgA0o9QE9R0qVuvDCP=HqVYBRfMmpaMZfiR_qkvRxhTLbg@mail.gmail.com> (raw)
In-Reply-To: <CAGNvRgD5JvsN2FJE=ndChOaQbLbXnE4RGAXJ8DJxfuXNU_K9WA@mail.gmail.com>

2017-03-12 13:16 GMT+01:00 Daniel Krügler <daniel.kruegler@gmail.com>:
> The following is an *untested* patch suggestion, please verify.
>
> Notes: My interpretation is that hash<error_condition> should be
> defined outside of the _GLIBCXX_COMPATIBILITY_CXX0X block, please
> double-check that course of action.
>
> I noticed that the preexisting hash<error_code> did directly refer to
> the private members of error_code albeit those have public access
> functions. For consistency I mimicked that existing style when
> implementing hash<error_condition>.
>
> - Daniel

I would just point out that I'm on vacations from Friday on for two
weeks, so if any changes to this patch are requested, I will work on
them after my return.

Thanks,

- Daniel

  reply	other threads:[~2017-03-21 21:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 12:16 Daniel Krügler
2017-03-21 21:26 ` Daniel Krügler [this message]
2017-03-23 17:50 ` Jonathan Wakely
     [not found]   ` <20190503224255.GI2599@redhat.com>
2019-05-04 14:36     ` Jonathan Wakely
2019-05-07  9:06       ` Christophe Lyon
2019-05-07  9:37         ` Jonathan Wakely
2019-05-07 10:07           ` Jonathan Wakely
2019-05-07 12:22             ` Christophe Lyon
2019-05-09 14:43               ` Szabolcs Nagy
2019-05-09 15:17                 ` Jonathan Wakely
2019-05-29 11:09                   ` Szabolcs Nagy
2019-05-07 15:27       ` Jonathan Wakely

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='CAGNvRgA0o9QE9R0qVuvDCP=HqVYBRfMmpaMZfiR_qkvRxhTLbg@mail.gmail.com' \
    --to=daniel.kruegler@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).