From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-64558-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 6274 invoked by alias); 20 Dec 2019 10:40:09 -0000
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
Received: (qmail 6264 invoked by uid 89); 20 Dec 2019 10:40:09 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=extremly, inconsistencies
X-HELO: mail-wm1-f53.google.com
Received: from mail-wm1-f53.google.com (HELO mail-wm1-f53.google.com) (209.85.128.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Dec 2019 10:40:07 +0000
Received: by mail-wm1-f53.google.com with SMTP id p9so8432469wmc.2        for <gcc-help@gcc.gnu.org>; Fri, 20 Dec 2019 02:40:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=oywfWZ4b9h0xBtZE10rhdNffmakkULS6R+wI3SoLMtA=;        b=Z265mXg7Wmufr+7XfElLw6OUDfLTfkAdtuPYWHTiwGxfALOw7gdDcVvF+6i+TlIh5K         JHZIJTLZYYsv5eK3/K1DBp4IjJ9JmR79/RqqTDq2xhccymdQ40BXqUUYM0U0y85sKIln         lOqX3vwCbOfL3sgSY1l+obBVsREihjuV3UscUy/VCCxESqeVAcYDcl8criS1ofDyV3jY         rsqchaj1C8HEO/9kOaeDVXaLY6dkLqyRTToNK2bUCr5ouGH0R2gu/3dhroGjREyQJYf3         kT7bMfUbUduRINVwuYGUlVITio9WMhxbasNCC144kIBfMkNSqdgp313Qf0mMNZJaNpLl         TIGA==
MIME-Version: 1.0
References: <bdc65575-bc43-a9b8-649f-bfd543f9ecb1@gmail.com> <CAH6eHdTE13TOvFePvrmyDtAnNkg8zf58XE1JBu1=nGrS2k3-2w@mail.gmail.com> <af60bce3-f092-6ecb-50db-bfbabc5dc00c@gmail.com> <CAH6eHdSyUpiOPr-kz-HvJ4FOB0DHamtszo+zpMy5Cc=ECbduOQ@mail.gmail.com> <506e00cb-ec34-cbc9-88dd-041da4e46462@gmail.com> <CAH6eHdRu+DXYFXB4dD_LNdQ1YD3vyoU4pUQpWxGcqOOKFtrkCw@mail.gmail.com> <1c8a64bc-c52c-b0fa-d38c-dfda875da790@gmail.com>
In-Reply-To: <1c8a64bc-c52c-b0fa-d38c-dfda875da790@gmail.com>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Fri, 20 Dec 2019 10:40:00 -0000
Message-ID: <CAH6eHdSv5w9+sy81FCSTkRR=_BaZUo_6uVYc4rB8ZsF9E7umug@mail.gmail.com>
Subject: Re: Spaceship-operator: why the data-members must be public / triggers ICE
To: Klaus Doldinger <klaus.doldinger64@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00107.txt.bz2

On Fri, 20 Dec 2019 at 10:30, Klaus Doldinger
<klaus.doldinger64@gmail.com> wrote:
> Am 20.12.19 um 11:25 schrieb Jonathan Wakely:
> > On Fri, 20 Dec 2019, 08:39 Klaus Doldinger, <klaus.doldinger64@gmail.com> wrote:
> >> But, how do I write a class to use as NTTP with private members?
> >
> >
> > You don't.
>
> Well, that is an extremly hard restriction, I think.
> Are there reasons for that?

Several. In short, they don't work very well and introduce
inconsistencies and warts to the language.

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1837r0.html
covers some of it.