From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33876 invoked by alias); 15 Jun 2017 21:25:16 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 33731 invoked by uid 89); 15 Jun 2017 21:25:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=H*F:U*jason X-HELO: mail-io0-f182.google.com Received: from mail-io0-f182.google.com (HELO mail-io0-f182.google.com) (209.85.223.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 15 Jun 2017 21:25:12 +0000 Received: by mail-io0-f182.google.com with SMTP id t87so19547375ioe.0 for ; Thu, 15 Jun 2017 14:25:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KzGljU1v7DmKPGx/tBQs5QHVlFyTRnk9mjvNK/Hq3lI=; b=Cam28/IpZZDQtFFIwL1lokoV0Titi4xKIuGmfJxZdPYaTz6wqo2vc4orZx2PAP0Hl8 0TOoFaq8VsllyZJ+4i0IaMEyEZCktDv7Gb1+ZtMQeYeZEW3uJTprcf73++RolV9Hueqj FS9y7bQ5Q2JAGW5CIRobesAc8ayL2qInnLpH1GdzmJl+tGvfdt3MystIcuiKLmV8DU6e iUFw6g3RETmZ/WP8mtuGpbW1idRLi2G83ZDJv0AjX3ycyK4aLgNuvoEQFfxhffEAF2Zs /h5ZAfQyi9D5yFoQwLz5YXbkaVMGDIDoaChChyG4fYXbeFPZ2NfiIG/4NZMSpObLtuK0 asWw== X-Gm-Message-State: AKS2vOxtEu10NwfMSoYsrspdboemT8HGVPFn7L1f+WcEGEPji+poPAQz sebFrk5PMxDJ8++6I5XBRpcE6MjVOJ7M X-Received: by 10.107.46.29 with SMTP id i29mr6934523ioo.192.1497561915792; Thu, 15 Jun 2017 14:25:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.20.139 with HTTP; Thu, 15 Jun 2017 14:24:55 -0700 (PDT) In-Reply-To: <620e2b9e-a77e-167d-52e3-0b34efa688a5@gmail.com> References: <620e2b9e-a77e-167d-52e3-0b34efa688a5@gmail.com> From: Jason Merrill Date: Thu, 15 Jun 2017 21:25:00 -0000 Message-ID: Subject: Re: [PATCH] document cp_operator_id and cp_assignment_operator_id To: Martin Sebor Cc: Gcc Patch List Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg01148.txt.bz2 On Thu, Jun 15, 2017 at 12:57 PM, Martin Sebor wrote: > Attached is a documentation-only change to add comments explaining > the C++ cp_operator_id and cp_assignment_operator_id macros. Hmm, I'd say that these macros return the identifier used internally to represent "operator OP" and "operator OP=", respectively. Looking up overloads is one thing you can do with that name, but the same is true of all identifiers, do we need to mention it specifically? Jason