Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120567 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77172 invoked from network); 13 Jun 2023 20:44:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Jun 2023 20:44:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7EA831804AC for ; Tue, 13 Jun 2023 13:44:02 -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=0.0 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 13 Jun 2023 13:44:01 -0700 (PDT) Received: by mail-ot1-f54.google.com with SMTP id 46e09a7af769-6b160f3f384so3660416a34.3 for ; Tue, 13 Jun 2023 13:44:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686689041; x=1689281041; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RJ5IoU6rIEQD0wpzMmHDARSdzm2a4x4mJJz2u2MjvtY=; b=iJlTtffOp0W0Ma5XiEm01sSn4OsICAywrXFMnQZFx0ZPgyRBB9LgjzhTuCdPWBtgZe h6GXkJwTOGZ8uQrvi67HrIpl2PeHt8NrZjaR+o0h/VEFWYdZbzh5o99rrI2fYWP63KQw aZBVXpwaqIRi0NPXVsqONgzQUlMhMOot78oKK/sQsBX0stWpSkP+AGC+o7py1v/ijtwB RsnD8zerOh+WnZvYYViZ4iMp07Y1P+C0qCuOBs1pep6OD9WgMHVQvQ+GVLfvS4O61Ncv 4mzN4DKoWYYOo/qIT2c/PX1iQDqf42rL+GmB7arQuRRaqI79DXliV+nznz09U8PLIMG0 DYAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686689041; x=1689281041; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RJ5IoU6rIEQD0wpzMmHDARSdzm2a4x4mJJz2u2MjvtY=; b=TSKZGa1A7N3hVeg/s54NN+5lHH3SZaiQ+9tCvBh5uYGHH66Z+Ft8tIb6jIcj6obgV2 FIwwAB+i5yewduJ0Efdt7cOtiCW0lBSBt5KuAqaGmQru2b45TvYbosHVTvyMjaHIxnmx 013lHHsGmHT3qsejMQGPY5uRYVCO9GCq6Omj0KPQX+6JWK8555iJFSrJq5+m8A/LQszc jPzOR83QRr1kO+dDuB0NQ1mNQ0jG9lZcMbqk2L191DFCp6padv1QhB+Q4mwGYpi4qqK+ PcQYTpKKxnIygKqMYnhUVspwq83mXp37nEyY4ovj//cZfVaSrju0eROORAapKzWaX+EU mjsg== X-Gm-Message-State: AC+VfDz/7krZNok4yZRGsA2cYoemKO97F2NdN1zf9xVFUO3mizJl3JzU bmjhrfLNfrCcaEEgkZq9IkE90mtnJpmsJBi3OE4ptuGbw6oWxA== X-Google-Smtp-Source: ACHHUZ6/+7jnCOMQAiAuF4tNYxciog0/QAn++/R37mIN6+aGMz81YiTHDCZ95I3sYMvwH8JgluJhMGJk0d8jS2cFLew= X-Received: by 2002:a9d:77d5:0:b0:6ab:2918:8185 with SMTP id w21-20020a9d77d5000000b006ab29188185mr11190719otl.5.1686689041200; Tue, 13 Jun 2023 13:44:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 13 Jun 2023 22:43:49 +0200 Message-ID: To: Levi Morrison Cc: PHP Internals List Content-Type: multipart/alternative; boundary="00000000000025ba4505fe08e5e0" Subject: Re: [PHP-DEV] [RFC] [Discussion] Clone with From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=) --00000000000025ba4505fe08e5e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (Resending my earlier message to Levi:) Hi Levi, I apologize if this has been discussed before, as I have fallen very > behind on internals discussions. I think it would be helpful to add an > example where the object being cloned accesses its properties. > Something like this: > > $b =3D clone $a with ["count" =3D> $a->count * 2]; > > If this is not valid, or if it has unexpected behavior or semantics, > that should also be included in the RFC. > It hasn't been discussed yet, but thankfully, there's nothing special about it: the LHS is evaluated first, then comes the RHS. Nevertheless, I've just clarified this in the RFC, and thanks for pointing this out! Regards, M=C3=A1t=C3=A9 --00000000000025ba4505fe08e5e0--