Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109742 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71015 invoked from network); 21 Apr 2020 09:43:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Apr 2020 09:43:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E4B241804B7 for ; Tue, 21 Apr 2020 01:15:05 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS 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-ot1-f54.google.com (mail-ot1-f54.google.com [209.85.210.54]) (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 ; Tue, 21 Apr 2020 01:15:05 -0700 (PDT) Received: by mail-ot1-f54.google.com with SMTP id z25so7061284otq.13 for ; Tue, 21 Apr 2020 01:15:05 -0700 (PDT) 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=r0tcoSs0n7iB2DL8J+1Rzndv0Ylt3p0kcjqvpqpXcuo=; b=gRgV9rZyDADE9EpXcHyLD+8Ri57tfBovaV+suOgp+YUG+6vSzO6LGwO5p/yKL3qvPE wE75Oy2bYuxcDO/pAWVRcnjPaVgowcuj7xYndnlLeFjPx/K+cM8Mk7Q2xi4aUdC75c/U L2A+ims7BgM8hcOSMn7DInaf3aiG01wEvpVPpzEbvkZOtrHjSCspVz8Iwpk8vD3S/0kw E5KUnaeuOad9A39Kd8pgS8HJ66QpV+UaB6mTixYxRy0C3ymspta7BMe/AuOWUXhFANeo eT+lczi/OCZprbE3I2xvoERbZeE9/po7zbCJdPTpDfzM1JYWdiPjLfDHIQiiytqk3OVm /Asg== 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=r0tcoSs0n7iB2DL8J+1Rzndv0Ylt3p0kcjqvpqpXcuo=; b=sAvsnilyiuTlcmtr30UXmSh5zvpEOKGOHS3fh7EVB/Yn2dH7p+qCb6mvcXzz0w0NBC A3oFwLpD4sOalUajJX8kLnMv2eikFwnduRn6T2kNnWwbgKWBgrP3Vv/1Tdgd8Ye8kq// mT5qXvYv29XK2FKZeMiHz7CjnU1nS10Cacp84A6Jj+7jSYUOeGOIf5MZ3lT2INYAYcve 4n3aqdVjXDPVa7aX1gFgse+pqtWld/z88a9IIfrbJHEKQwWd62nc6JZaycHupM+kwBOL ddcwpsZidB4/VRFg9LagokDwljhJ0gSF7IUsPjzGfPcsHlaawY0NIw0ylDW2MXwwwhw1 o01Q== X-Gm-Message-State: AGi0PuZtp3EJhqrpBlUHUkCnYrc6tZZxF2LHT8XEVYf14vEmCSrOE2kX kH11H7b7LWHgrjRhclM1zVl/MADVV7UweJ5N3xk= X-Google-Smtp-Source: APiQypKhPEO+a0sKT6mtNsgyksp5WerKQEB0cwYLs/59b57VVOtr4DnO4BgvX/J9r9RIDT/5LFVKcNZ2o7tWlBLwnRw= X-Received: by 2002:a9d:22c9:: with SMTP id y67mr12371459ota.36.1587456904902; Tue, 21 Apr 2020 01:15:04 -0700 (PDT) MIME-Version: 1.0 References: <5e9e1335.1c69fb81.9a507.b80cSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Tue, 21 Apr 2020 09:17:13 +0100 Message-ID: To: Marco Pivetta Cc: Andrea Faulds , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000e9c59305a3c89c29" Subject: Re: [PHP-DEV] Re: [VOTE] Attributes v2 RFC Vote is open From: petercowburn@gmail.com (Peter Cowburn) --000000000000e9c59305a3c89c29 Content-Type: text/plain; charset="UTF-8" On Mon, 20 Apr 2020 at 22:36, Marco Pivetta wrote: > Hey Andrea, > > On Mon, Apr 20, 2020, 23:25 Andrea Faulds wrote: > > > Hi, > > > > Benjamin Eberlei wrote: > > > Hello, > > > > > > I have opened the vote on the Attributes v2 RFC. The voting will be > open > > > until two weeks from now, May 4th 2020, noon UTC. > > > > > > RFC: https://wiki.php.net/rfc/attributes_v2 I know that I'm "too late" to be making suggestions, but I would like to see a new "@@" operator over the proposed <<...>> or @:. While it is possible (!!) that some code is already using a double @-operator in a way that would conflict, I'd posit that it is a reasonable BC break in return for a subjectively nicer (for want of a better word) attribute operator. Nikita and Sara shared similar grumblings in unofficial channels [1] [2]. However, there is something to be said for just deciding on *anything* and rolling forward with it. [1] https://chat.stackoverflow.com/rooms/11/conversation/at-at-01 and https://chat.stackoverflow.com/rooms/11/conversation/at-at-02 [2] https://www.reddit.com/r/PHP/comments/g4psl5/rfc_attributes_vote_is_open_now/fnz97fk/ > > > > > > > Thank you everyone for taking part in the detailed discussion. > > > > > > greetings > > > Benjamin > > > > > > > Thanks for putting this to a vote. I remember I had some comments about > > autoloading behaviour and you changed the behaviour in the RFC, but I > > didn't get around to reading it again. I am concerned though that it > > doesn't seem to say anymore when autoloading happens, if at all? Can > > that be clarified? > > > > Thanks, > > Andrea > > > > From my review of the tests, autoloading occurs when an object is being > requested (via `newInstance()` call on a reflection attribute). > > Until then, the same semantics as the `::class` pseudo-constant apply. > > > > --000000000000e9c59305a3c89c29--