Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110377 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 82556 invoked from network); 4 Jun 2020 19:07:04 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Jun 2020 19:07:04 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EFA20180564 for ; Thu, 4 Jun 2020 10:49:30 -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-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) (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, 4 Jun 2020 10:49:29 -0700 (PDT) Received: by mail-wr1-f49.google.com with SMTP id r7so7110157wro.1 for ; Thu, 04 Jun 2020 10:49:29 -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=VT5K5Ytyxof4Wb4W7PJ6kkOvw9woCs4zbLkwowmNj4M=; b=cq4QcajxFQJKDliIb+om2QZSSDsEpaKp5s3RVmFHaLzsb1n0R42T+RqwBVQ09JDG+u LnccIbQrmknKh6BLTYCQ+To3wFbaPebCmjGE4c5dfiLGhcx/laMVq4dNmEivCGmIugnP k+L+oOGgjK/79driqvTIIqrLieaO8rcNhElhdgcO/e1tGY1z9O9cUTxpCWanv0rDTx/E vqYyOVkRG2PAc/BYnmwBMjAKJ9tEhJLsXWUcNshrJt6KK5/9/d4Gc4qnj9TjPPjg8PVI edXlSW+LTd+OJ/vbzKGi3jgKJrYAHZvJsOZxVtoZvDLATM0Ae6PQnaRH3fy6tJelfJgn /mcA== 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=VT5K5Ytyxof4Wb4W7PJ6kkOvw9woCs4zbLkwowmNj4M=; b=fDSlWc0FIrXh+TUPu30JJMlIE0xF4r3d94FPFSZh19YMP1D6mQRZLMZ7U52CncbJVf +0UQZWxJ6M7dj+mE7NoX0SfhQATetjSSIN8IYN0/ieeCGojBHkYumI3P0eTUSpMQnOjQ QvlDWabH94GWusl/UMSEix/TfIFLM9hTRzBUs+GZ3NEnYZGlKcc72ClNNCtx4PWkF8Ki nXlS3OwQcWkJRif6tuyrbGCHXsFvtjCPK2kIY+4onxbm06lczfAKaPQbU35m0NJR3Uhh w6hHh2gOb5BvY5B0L5BKXhkXhP144U9UnCvzSLyRlDswJo+2qSY1sIrOWmhIUvSArNoK ztAw== X-Gm-Message-State: AOAM530CaQj2o67g0X2wxthwsEAtrKwaIK5CAookyDv0fjwNg0r313nY owFnvsbRqbRVM/kaHEGj1/0pDZ3bytbFijPf58T1Xw== X-Google-Smtp-Source: ABdhPJwbtntSCzWtEw3l7Q22iStnv0cdrI4HhvCUTLcTM819LEZ+4fBHMEU4PvQqRX9b7HXckSMjKiU2M1ax1gik/7s= X-Received: by 2002:a05:6000:1185:: with SMTP id g5mr5995434wrx.39.1591292967131; Thu, 04 Jun 2020 10:49:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 4 Jun 2020 19:49:16 +0200 Message-ID: To: Benas IML Cc: PHP Internals Content-Type: multipart/alternative; boundary="0000000000000a333305a745c400" Subject: Re: [PHP-DEV] Re: [RFC] Amendments to Attributes From: kontakt@beberlei.de (Benjamin Eberlei) --0000000000000a333305a745c400 Content-Type: text/plain; charset="UTF-8" On Thu, Jun 4, 2020 at 12:54 PM Benas IML wrote: > Thank you for the update! Given that there is still an open issue, is the > RFC proposing flags or a separate `<>` attribute? > Good point, we came to the conclusion to simplify. Should attributes be in the global namespace, then we shouldn't arbitrarily add more, so it will be a flag. At that point, because you rarely declare new flags we decided to merge target and flags and only have one flag. You could do the following: <> > > Best regards, > Benas > > On Thu, Jun 4, 2020, 12:29 PM Benjamin Eberlei > wrote: > >> I have changed back the rename from namespacing to Attributes\Attribute to >> using just Attribute after a few discussions off list. The reasoning is >> that it becomes more clear that a majority of core contributors strongly >> prefers using the global namespace as the PHP namespace and opening up >> this >> point again makes no sense. So the state of the RFC is again what it was >> when I originally posted it with renaming PhpAttribute to Attribute. >> >> Unless there is some new significant feedback I am going to open up this >> RFC for voting on Monday next week. >> >> On Wed, May 20, 2020 at 7:07 PM Benjamin Eberlei >> wrote: >> >> > Hi everyone, >> > >> > the Attributes RFC was rather large already, so a few things were left >> > open or discussions during the vote have made us rethink a things. >> > >> > https://wiki.php.net/rfc/attribute_amendments >> > >> > These points are handled by the Amendments RFC to Attributes: >> > >> > 1. Proposing to add a grouped syntax < >> > 2. Rename PhpAttribute to Attribute in global namespace (independent of >> > the namespace RFC) >> > 3. Add validation of attribute class targets, which internal attributes >> > can do, but userland can't >> > 4. Specification if an attribute is repeatable or not on the same >> > declaration and fail otherwise. >> > >> > Each of them is a rather small issue, so I hope its ok to aggregate all >> > four of them in a single RFC. Please let me know if it's not. >> > >> > greetings >> > Benjamin >> > >> > --0000000000000a333305a745c400--