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áté Kocsis . Rowan Tommins <rowan.coll...@gmail.com> ezt írta (időpont: 2020. febr. 15., Szo, 0:07): > On 14/02/2020 13:42, Máté Kocsis wrote: > > Maybe only if our long-term goal would be to deprecate/remove > > non-typed properties and implicit initialization altogether in favour of > > 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é Collins) > [IMSoP] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
