Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111261 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21290 invoked from network); 30 Jul 2020 13:54:38 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Jul 2020 13:54:38 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B90361804DA for ; Thu, 30 Jul 2020 05:50:58 -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-f68.google.com (mail-wr1-f68.google.com [209.85.221.68]) (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 ; Thu, 30 Jul 2020 05:50:57 -0700 (PDT) Received: by mail-wr1-f68.google.com with SMTP id y3so24789632wrl.4 for ; Thu, 30 Jul 2020 05:50:57 -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=ltOaOxUyQmafSRnUj1RwqoWQ+yRXV/kXEnhEvmEFfac=; b=lOoD7BAOFpuYYQXpMvW+YT8AG0vV8HBCxKcvEQGcDC8tjiRKjJjqKhwPqmbvlQPkFd qEugCWFQkeQ6Jci4ZAlqBgdSxf/lnvRQPmnDy33nWP731HHG331baz3ZLp2rfYHk+fcT 7qC4H0T8dLPDna5FFhOxU+RYKcdOWhEEoVmkFITC/k2oa1cfFVrrA/yPQYOxVGV5+ttt cfpOq71biL3n5aOOFfTgqcebHQr1ThxpPiiHozMCqhTQU0OWHa5Z3ZNCLvLU8GVuwo08 zzOBBjf6IHeitdkmote0lhaRJUk51ZhOeVwJayEjZuxh8ynoBvVvYCHozrPBirB9gDOB frlQ== 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=ltOaOxUyQmafSRnUj1RwqoWQ+yRXV/kXEnhEvmEFfac=; b=F5bxEdP5A3weivT2ADaKrP+UVMmdE6B0vXPFXYi662c0M8VrWOCytMERJmJyiV4yU5 Hv+BSg8yomdl+KPYbaBja1s2xDodzqdsqfUxwmvzo+GKMI7Y4tFoqCBKCM0qdfRxEyx2 c25MxmMtPZ8vF/aykHYtuULlgkUsZbye5cpNLRvY41lnh9EsTHmFHYNvXhLB9O4SSdGa zA3L+l4sEUOxRvc8OYYRIK9UGNtdKRKkoXkCMjxEXZOfwWF3Y831dmxkFb3hcHpo7HTK GFGIkX/eQMBQuXcUUN1JH8E6MWe94ycIz0LwSXrGYyBZuFHOwq35vietikLkxG4ybpRB ZKfQ== X-Gm-Message-State: AOAM533pe5vPeFQcoIg7trFbQ1kA2rsM+NGWRXq0Smdx2sKPt35Yn90p SNVo9Mwzk4htEdx2PJyOQoPcTKzkw2CD43zUISvTHBOvRP8= X-Google-Smtp-Source: ABdhPJwDs+I+JTuvBXuTerIH+5aMl6g2KT/BMDiTZ4/CSAsUm8LeTH09JmALGGTHOMFTc0x0micfcdazTvmtH1Y2YnM= X-Received: by 2002:adf:ce89:: with SMTP id r9mr2906955wrn.116.1596113454828; Thu, 30 Jul 2020 05:50:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 30 Jul 2020 14:50:43 +0200 Message-ID: To: Joe Ferguson Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary="0000000000007f284905aba81fa5" Subject: Re: [PHP-DEV] [RFC] [Discussion] Shorter Attribute Syntax Change From: kontakt@beberlei.de (Benjamin Eberlei) --0000000000007f284905aba81fa5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think it has become clear that we need to revisit this syntax question again, including the elephpant in the room of delaying this feature to 8.1. The reason is not only Joe's desire to revote on #[], but also that there are now more syntax proposals such as @[] by Derick or @@ in comments by Tyson (though no patch exists for it yet). At this point a lot of syntaxes are potentially viable (except single @, please don't suggest it). I feel the choice between many syntaxes is 80% subjective, 20% objective facts, so tensions are to be expected. As the author of the original RFC and patch, I hope I have some klout in suggesting the following procedure (RMs would need to extend their approval for revote to this). 1. we collect syntax proposals once again, with the requirement of a simple patch being available against php-src/master for viability in 8.0. 2. RMs are the arbiter to decide the patch is acceptable to be included for 8.0 or if its selection would delay entire attributes to 8.1. 3. I would make a feature matrix for the vote / RFC page and sort each proposed syntax into it, seeking input from the proposers. 4. We would then hold another vote on syntax using STV where the choice is a combination of syntax and target version, examples: - <<>> in 8.0, #[] in 8.0, @@ in 8.0 (all these patches are viable) - @@ in doc blocks for 8.1 - =C2=A7[] in 8.1 (weird example to demonstrate the point) and so on. The STV vote would run with potentially 5-10 different syntaxes. On Time Frame: Sara allowed to extend this decision into feature freeze, but I believe it shouldn't be later than Beta 2 (August 20th), especially if the outcome could be delay until 8.1. What do RMs think of voting from 10th to 17th of August, giving us 3 days to merge. This gives everyone until August 8-9th to work on their syntax proposal. greetings Benjamin On Tue, Jul 28, 2020 at 4:47 PM Joe Ferguson wrote: > Hello Internals, > > I've been working with Derick Rethans and others (thanks all!) on a Short= er > Attribute Syntax Change RFC which outlines reasons why the "#[]" syntax > would be preferred over the currently agreed upon "@@" syntax for Shorter > Attribute Syntax. > > An important part of the research that went into this proposal demonstrat= es > how "@@" will make handling attributes more difficult for PHP_CodeSniffer > (and similar tools) and shows how the alternative "#[]" syntax is more > friendly for these tools. > > You can find the RFC > https://wiki.php.net/rfc/shorter_attribute_syntax_change and I'm happy to > answer any questions as best I can. > > -- > - Joe Ferguson > JoeFerguson.me > osmihelp.org > --0000000000007f284905aba81fa5--