Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108598 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38656 invoked from network); 15 Feb 2020 16:20:16 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Feb 2020 16:20:16 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B16331804AB for ; Sat, 15 Feb 2020 06:35:10 -0800 (PST) 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.8 required=5.0 tests=BAYES_00,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_H2, 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-vk1-f181.google.com (mail-vk1-f181.google.com [209.85.221.181]) (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, 15 Feb 2020 06:35:10 -0800 (PST) Received: by mail-vk1-f181.google.com with SMTP id o187so3413185vka.2 for ; Sat, 15 Feb 2020 06:35:10 -0800 (PST) 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=iW74ytXrOvzWfov1RuSICG9pqotHA5N46sZtFgWCG8Y=; b=jQOkCwXXMDwGe1lpzYVXxjSWwYEIa4371uhMeaaRFhzmTVYV7I1p2jGenfxH7SPsLW 3nQf1biv8vJiBnmJi1owizTVCvYQlx+Ti2qjCrKWvJe2PvVcDOO+Ba1p6V2Fncpo5A5Z g1ZJvW14X5CgNQYoRW6Z+MfSOEf3IaWaVB3huFCwlIPDdsVaiPWVOSfUgjbxAyI/jnrK RoheXhPGt7e05VMQpt7vs3REuzMuyGpXpWn4GGz5nGfeopYBfXEKkoFx3imJx1uxbSTF tv7BFsuDJbAkgzSzugKo1x0U2wCp9vj5N1ACPH35n/EdZpbkkv5ozkj9qz61uFadus1W VsZg== 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=iW74ytXrOvzWfov1RuSICG9pqotHA5N46sZtFgWCG8Y=; b=HhcZJjBGd0waEUg7F2wxhWbPMwDMSlMIyD6qqm72sNaJK6mATrEKcvul6x1G2u9rgC D/AwEBaBNe9HlW0CjfB+3q4ken57tX6F+FA3yEblWMnyW1jD9YtuYx3X61fA3x1idspA zDy/chrJbQaXwVGSrrdRwJwzvtabBhohI421uE1zri12JOnBJZC2miw/wGHFsxZsWyi/ SxVCx3imndgXiZgRAwbksq3OjPD7b8Mq+s1m+q0F3wu3VL08iA72mcESwhBuGqdnMrHy OrBWQU2SAPRf/Ww8fhd03FywPKDjQL+L6a05u9EmuNZO/uoJMZnqtOa5Q87lCJB7TNxm hJ+g== X-Gm-Message-State: APjAAAWCpRalLCZFVMjushHj/Zjv/NgBIyhsl7P2Oqr3SirxuiZavx7e 7BrVtOQVioa/AkgtThG9ldtfceiPiM9FXAWJwOg= X-Google-Smtp-Source: APXvYqzfvVd65yLIj4HkZKK514oGn2ixIFMTWLIalkc8+DxUkG1zyT22wS9Go6jY2bwShUhKwC3sPNRysylidHARHtc= X-Received: by 2002:a1f:6344:: with SMTP id x65mr1802740vkb.26.1581777308683; Sat, 15 Feb 2020 06:35:08 -0800 (PST) MIME-Version: 1.0 References: <65f5055f-ffba-0042-7af7-5b122e98933f@gmail.com> In-Reply-To: <65f5055f-ffba-0042-7af7-5b122e98933f@gmail.com> Date: Sat, 15 Feb 2020 15:34:58 +0100 Message-ID: To: Rowan Tommins Cc: PHP Internals List Content-Type: multipart/alternative; boundary="00000000000099123e059e9e3a45" Subject: Re: [PHP-DEV] [RFC] [PROPOSAL] Immutable/final/readonly properties From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=) --00000000000099123e059e9e3a45 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rowan, I'm also on the opinion that making the mixed type the (implicit) default is not a good idea. However, I believe the uninitialized state is useful, what's more, it was unavoidable in order to properly support non-nullable object properties. But I don't want to make a case for this decision as it's too late now. :) > Immutable properties, and eventually immutable objects, however, are something I'd be very interested to see. I am happy to hear! M=C3=A1t=C3=A9 Kocsis . Rowan Tommins ezt =C3=ADrta (id=C5=91pont: 2020. = febr. 15., Szo, 0:07): > On 14/02/2020 13:42, M=C3=A1t=C3=A9 Kocsis wrote: > > Maybe only if our long-term goal would be to deprecate/remove > > non-typed properties and implicit initialization altogether in favour o= f > > mixed type and implicit uninitialization... > > > Can I just leave an "ugh, please no" on this part. I remain of the > opinion that the introduction of the "uninitialised" state was a huge > mistake, and we should be actively working towards making it > unnecessary, not building more features that rely on it. > > > Immutable properties, and eventually immutable objects, however, are > something I'd be very interested to see. > > > Regards, > > -- > Rowan Tommins (n=C3=A9 Collins) > [IMSoP] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --00000000000099123e059e9e3a45--