From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 1FDB43858D38 for ; Tue, 7 Feb 2023 21:18:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1FDB43858D38 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675804683; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=p4Vu7+Hc2ktKUSonNMuRIxxJ50OlAZ5JB9VfJ6AcJ7Q=; b=YArAqseOr25Xc5HPGYNH588OVPLh54jSfIHodEas0/A0SAgxUoAIPSLgd/PSII27D2TKST XMDKROmpBap4VKy1Tzd/w8MjoxG56WT6PxYH/Fv/f2ubbhGd6FpGZubeLk/s3ad2F7nB7P dYyt0OD+X371RQs0CAWp9UbDNK36yoc= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-605-7e0tKOaWNPaOpNkoN7M-Ug-1; Tue, 07 Feb 2023 16:18:02 -0500 X-MC-Unique: 7e0tKOaWNPaOpNkoN7M-Ug-1 Received: by mail-lf1-f69.google.com with SMTP id c29-20020a19655d000000b004db074001d4so1094548lfj.19 for ; Tue, 07 Feb 2023 13:18:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=p4Vu7+Hc2ktKUSonNMuRIxxJ50OlAZ5JB9VfJ6AcJ7Q=; b=VxKKiuvMiZZ98IguwDxnuz1nhhPUJ3f7HPVj7Fh+x5qJKqilo7YFg1qpqAsbgLxPAn Riuth/3EgtHx4mBVsN+Q/hwX+JlSxY1d/+Jjwx7/Syb9PI4m2BBnUUaimIAlzjrYpMO8 i7mZR2Vo/S0FQLt7qh5KABqbDTio5cS9r8qgfb9wsFz2BS2uEyUmFXDDR3Gw36GBsQ5T 4qzVbjoas+WshhFcG6+3WMFRKq5As8iwHrRhSuwWqzVk26xeDtTSRWo/elTOKTI+9mOF rvzniB5RLbLM5gaAcMMzj7z/iN2x2E3/LJKld1sea+T6PCebGMewCN/VNyNVR7+7c+ia Oxaw== X-Gm-Message-State: AO0yUKUtQRcUb6LlwI+pZFT2s1Ic6nYSj9Ksa06f4WFEQneSmrK3SO1M NzQfcPBsZn4+bI4GEu/CH+R+/xPy+7BCPHlnbUevs0WSo/Z4afZzlag5AZm8z3rnsCwTASu3m3d ql8e3A8u87mzCab4WL2hZoikfUDhCj2o= X-Received: by 2002:a2e:4c02:0:b0:28e:1ca4:b62 with SMTP id z2-20020a2e4c02000000b0028e1ca40b62mr738649lja.97.1675804681074; Tue, 07 Feb 2023 13:18:01 -0800 (PST) X-Google-Smtp-Source: AK7set/iHwnnwXEbeWCQCqt4StaQq0U10AQvVbc58YdjCjYR8mJLFLnnGaQKEXFllnGOue+9fRFnt1ufWiOHlfJl0j8= X-Received: by 2002:a2e:4c02:0:b0:28e:1ca4:b62 with SMTP id z2-20020a2e4c02000000b0028e1ca40b62mr738646lja.97.1675804680741; Tue, 07 Feb 2023 13:18:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Tue, 7 Feb 2023 21:17:49 +0000 Message-ID: Subject: Re: Add clang-format for libstdc++ To: Dimitrij Mijoski Cc: "libstdc++@gcc.gnu.org" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, 7 Feb 2023 at 20:39, Dimitrij Mijoski via Libstdc++ wrote: > > Is there interest to add a clang-format file for libstdc++? > > The basic idea is to take the existing clang format located at contrib/clang-format, > copy it to contrib/clang-format-libstdc++, and modify it according to libstdc++ rules > https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_code_style.html . > Similarly to the first clang-format, it will be optional and it will be enabled if the developer > calls the command: > > make clang-format > > inside the build tree. That will create the symbolic link srcdir/libstdc++-v3/.clang-format . > Alternatively, it can be put directly where it is required without the need for the invocation > of make. If you want to do the work and contribute it, please go ahead. But last time somebody looked into it, clang-format doesn't support our code style conventions. There was something in our template indentation that clang-format doesn't support, and can't be configured to support.