From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Ville Voutilainen <ville.voutilainen@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
libstdc++@gcc.gnu.org
Subject: Re: [libstdc++ PATCH] Implement observer_ptr
Date: Sat, 02 May 2015 12:50:00 -0000 [thread overview]
Message-ID: <5544C7F5.2080305@verizon.net> (raw)
In-Reply-To: <20150502094224.GR3618@redhat.com>
On 05/02/2015 05:42 AM, Jonathan Wakely wrote:
> On 02/05/15 10:40 +0100, Jonathan Wakely wrote:
>> On 01/05/15 22:02 -0400, Ed Smith-Rowland wrote:
>>> On 05/01/2015 05:01 PM, Jonathan Wakely wrote:
>>>> On 01/05/15 16:37 +0300, Ville Voutilainen wrote:
>>>>> Tested on Linux-x64.
>>>>>
>>>>> Implement observer_ptr.
>>>>
>>>> Thanks! Committed with some minor formatting changes.
>>>>
>>>> I've also committed this to add feature-test macros and update the
>>>> docs. Tested powerpc64le-linux, committed to trunk.
>>>>
>>>>
>>> I pretty sure we're supposed to add the macro for *all* the headers
>>> that got enable_if.
>>
>> That's not how I read the Fundamentals TS:
>>
>> Programmers who wish to determine whether a feature is available in
>> an implementation should base that determination on the presence of
>> the header (determined with __has_include(<header/name>)) and the
>> state of the macro with the recommended name.
>>
>> And the header for erase_if is listed as <experimental/vector>.
>
>
> And SD-6 says:
>
> For library features, the âHeaderâ column identifies the header that
> is expected to define the macro, although the macro may also be
> predefined.
>
>
>
OK. Thanks.
I do remember an SD-6 discussion about how annoying the
define-the-macro-in-all-relevant-headers was.
I didn't know there was a resolution. I need to reeducate myself.
Meanwhile I'll rollback my patch.
Reverted in 222722.
I'll ask next time.
Sorry for the noise.
Ed
next prev parent reply other threads:[~2015-05-02 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 13:37 Ville Voutilainen
2015-05-01 21:01 ` Jonathan Wakely
2015-05-01 21:26 ` Jonathan Wakely
2015-05-02 2:02 ` Ed Smith-Rowland
2015-05-02 9:40 ` Jonathan Wakely
2015-05-02 9:42 ` Jonathan Wakely
2015-05-02 12:50 ` Ed Smith-Rowland [this message]
2015-05-02 13:01 ` 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=5544C7F5.2080305@verizon.net \
--to=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=ville.voutilainen@gmail.com \
/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).