Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114121 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 91078 invoked from network); 24 Apr 2021 14:00:16 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Apr 2021 14:00:16 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5E2A41804CC for ; Sat, 24 Apr 2021 07:03:47 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 24 Apr 2021 07:03:46 -0700 (PDT) Received: by mail-wr1-f51.google.com with SMTP id x5so902100wrv.13 for ; Sat, 24 Apr 2021 07:03:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N9UQqSOwR/1NHIZSrCUw2v0YAWunDGj3VZG5XejR5WE=; b=sDM7CJyJ+im/A7y6AQP/j8lxLC2EWTks36Izi5LfgAaXT6oge9TLHwrakTXDplKHEv +GN3L3lt3lVVD99SgL2xp9AYsz+2+VTGxE7asCDzp2yI5VsNZmZot4IMIPi8Jx3TS8OX JMq513lMDbBc4c/WXjTgkZx81Vh+aOIzfmPui5yPDgHYOit+CHmLWHntkW6Zu9voLoQQ 7ENHK0ksVer9XMJqD7t2Ova+swFPbHfzflCA4wdguuTAw9fUFsNeRDgb6gfFLxvpZ3qK 1ukaYNjtrwe4Ul+PT5qpuyZkB6l/OxNntD+bubaQuLV2jQ4HtuUvgR6D6U1NqI2Omsvy 4tDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N9UQqSOwR/1NHIZSrCUw2v0YAWunDGj3VZG5XejR5WE=; b=ja/RvUa+ZLdt17hhtbC/qg3sI/Yp3loBKb3j2NW6YCRBTu0XU9e9nG+LWfz7KG672D W293wNOHm14yCca2TxKRqQ8VEGLZ1agfuxCZh+4lmGkDTQwxdfeLZCM9mEp4sLqvx5zG HaWli+WJ+a91MmgEl12ax0JBPNleJNNkYIhieXtQ3yeO8jUJw/qs4DqVQIMBKuV5Gse0 RMebI0S7hUE/dZdq8UrrlwTI0iAkeOUR638h6ssOnXPUs/IX+ZMcemfjTdbtqDNQTBq1 OvECv6o4g3FezyNATIYTUccPND/AHCYaEeuhgD3TpUvujhBNnR6RWTf0+XUYD7/9Seg1 iqJA== X-Gm-Message-State: AOAM531FZ46dmonrGRBH/Pf03i+5QPh2tbvvVU603Vf1Ri8+c3XO0WYs e678DdmYdkBwK5+RBwUijDie1V5Zgit5efkCy1nPwj/jDZY= X-Google-Smtp-Source: ABdhPJzgKwT5517klZ7PPfftX0riu8czij5eBPxngfaLipDYDNkPC3H22gvi0sIk7G/HzM74d3ke3EA4O0bBXI50rnc= X-Received: by 2002:adf:ea83:: with SMTP id s3mr11046630wrm.39.1619273023333; Sat, 24 Apr 2021 07:03:43 -0700 (PDT) MIME-Version: 1.0 References: <5b9f1500-615a-48f1-815f-1d48b327ef90@processus.org> In-Reply-To: <5b9f1500-615a-48f1-815f-1d48b327ef90@processus.org> Date: Sat, 24 Apr 2021 16:03:32 +0200 Message-ID: To: Pierre Cc: Saif Eddin Gmati , PHP Internals Content-Type: multipart/alternative; boundary="00000000000059b7f505c0b861ee" Subject: Re: [PHP-DEV] [RFC][Draft] Sealed Classes From: kontakt@beberlei.de (Benjamin Eberlei) --00000000000059b7f505c0b861ee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Apr 24, 2021 at 2:56 PM Pierre wrote: > Le 24/04/2021 =C3=A0 12:55, Saif Eddin Gmati a =C3=A9crit : > > Hello Internals, > > > > I'm sending this email to open discussion about sealed classes, > > interfaces, and traits feature for PHP 8.1. > > > > I have create a Draft RFC here: > > https://wiki.php.net/rfc/sealed_classes > > > > > > A major concern for few people have been the syntax, in which it > > introduces 2 new keywords into the languages, therefor, i have added a > > section about alternative syntax which could be used to avoid this > > problem. > > > > Regards, > > > > Saif. > > Hello, > > And why not using an attribute, such as in HackLang ? > +1 on this, I said the same on the "never/noreturn" RFC. There is a much less invasive way to add new keywords/flags to functions by using attributes. Imho this decouples new features from the language and reduces the "risk" of adding them to the language. That should increase the likeliness of it getting accepted in my opinion. > > Regards, > > -- > > Pierre > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --00000000000059b7f505c0b861ee--