Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96904
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain honestempire.com designates 66.111.4.26 as permitted sender)
Message-ID: <1479254409.563911.789059065.16D4C9A4@webmail.messagingengine.com>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
Date: Wed, 16 Nov 2016 00:00:09 +0000
In-Reply-To: <CAEUnE0cZZekzemtfBBO71uc_3JcTsR9gouzXT5okhavqbvDYJg@mail.gmail.com>
References: <CAEUnE0cZZekzemtfBBO71uc_3JcTsR9gouzXT5okhavqbvDYJg@mail.gmail.com>
Subject: Re: [PHP-DEV] Type locked variables
From: daniel@honestempire.com (Daniel Morris)

On Tue, 15 Nov 2016, at 11:44 PM, Michael Morris wrote:
> Note this would simplify one of the use cases of setters - insuring the
> class member is of a valid type.

It's already possible to ensure within a setter that the variable is of
a specified type, you only need to make the instance variable private
and scalar type hint the method arguments within the setter (provided
that strict_types is set), I think this would be more likely to lead to
code littered with calls to unset rather than to provide much benefit,
and as far as I'm aware, there's no real performance benefit that can be
gained from this as of yet since the variables will still be a zval
internally.

--
Daniel Morris
daniel@honestempire.com