From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) by sourceware.org (Postfix) with ESMTPS id 923173858D20 for ; Sat, 25 Mar 2023 13:04:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 923173858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=cs.washington.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.washington.edu Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-5456249756bso84580837b3.5 for ; Sat, 25 Mar 2023 06:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.washington.edu; s=goo201206; t=1679749488; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uczsInHTDNkJfX7zV8mHqXyCnbghbiICASxZ59cC+UU=; b=EWNpX7DqT0YHiAd8zPhpfDxCgUaEG1T2aXzbfNNwllkOPhUu/LS4dwG0TfZ0iAeENN vu13PJNeAkKRxlTViQjE91H0K2OdRb76lKSWMW0RYd5ngz9lE2BR3YZCVTDbAtKQMlZf QQ8h6vGtSKFdq2RzNDmlK4KM4/QmDceLLZIfg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679749488; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=uczsInHTDNkJfX7zV8mHqXyCnbghbiICASxZ59cC+UU=; b=bP6kzkfJ7oLBAs2kzRAzA0BUPZectIDPOwVZTW/+dR1BHHsayPdyscYrZeAa78ddtq 8REp9VvAlvDu4+2HMx3cupseZveKiz5QDuzKwe5rDFkJQ92Nyke1aKPDYzhbjJKxzExk Vxl77Xs3iwZqNvLVKetCJ+J1uDJuikN+KWljF6Lfp0F0ucEEnJOL09NXDXpPySj6QOgU JYsjOLq8DKo8uvHhNlmyajv2Xd0OphIZzjJpdZE/Qx1Ngwt8YKg5+oFIlGbG1MP0kKFm VZPUTT2uC1AjbavavLTaz4nna88rJ/Jcix0UEDNU9JeaXX0u0LUkFXOBRdubThdXjXIq QEFw== X-Gm-Message-State: AAQBX9fGn/xjnp2Kk+qJtEpB7IzaQU4LsdnuX1iX1v3nLhKg+HzPkoNV jyB/BT2RdpjQXFz0mT/M1H1YJ9lFn8wr1AjXQtlFOpDBOcej8UlOyD8= X-Google-Smtp-Source: AKy350a+/50GrOXeoEivIPEot2RZbLLsnI0spHdZFbUKpBbaW4lE0l7VuoKiH6/PFtJlxwKcMIqthKfayOTwNtDs9vc= X-Received: by 2002:a9f:350d:0:b0:764:64c1:9142 with SMTP id o13-20020a9f350d000000b0076464c19142mr6301058uao.0.1679730814130; Sat, 25 Mar 2023 00:53:34 -0700 (PDT) MIME-Version: 1.0 From: Ken Matsui Date: Sat, 25 Mar 2023 00:53:23 -0700 Message-ID: Subject: [GSoC] Conflicted Built-in Trait Name To: gcc@gcc.gnu.org Cc: "libstdc++" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DATE_IN_PAST_03_06,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, I am working on the GSoC project, "C++: Implement compiler built-in traits for the standard library traits". Built-in trait naming simply adds two underscores (__) to the original trait name. However, the same names are already in use for some built-in traits, such as is_void, is_pointer, and is_signed. For example, __is_void is used in the following files: * gcc/testsuite/g++.dg/tm/pr46567.C * libstdc++-v3/include/bits/cpp_type_traits.h In this case, are we supposed to change the existing same name in the code to something like ____is_void (four underscores)? Or is it better to break the naming convention of built-in traits like __is_void_builtin? Sincerely, Ken Matsui