Re: [VOTE] Scalar Type Hints
| From: | Lars Strojny | Date: | Sat, 07 Feb 2015 03:36:45 +0000 |
| Subject: | Re: [VOTE] Scalar Type Hints | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82079@lists.php.net to get a copy of this message | ||
Hi Andrea,
> On 05 Feb 2015, at 21:14, Andrea Faulds <ajf@ajf.me> wrote:
> [...]
> Voting starts today (2015-02-05) and ends in two weeks’ time (2015-02-19). In addition to the
> vote on the main RFC, there is also a vote on the type aliases issue, and a vote to reserve the type
> names for future RFCs’ sake if this RFC fails.
>
> The RFC can be found here, and it contains a voting widget:
> https://wiki.php.net/rfc/scalar_type_hints
I realise how much effort you put into making scalar type hinting possible in PHP and I applaud you
for that. Being a proponent of strict scalar type hinting I also understand the current RFC tries to
find a compromise between both camps. It is probably the best we can come up with right now given we
want to fullfill the following set of requirements:
- Strict scalar hinting
- Weak scalar hinting
- Let the mode be chosen by the caller, not the callee
I nevertheless decided voting against it as I am afraid the current RFC would do more long-term harm
to the ecosystem than not having scalar type hints. My main concern is that the declare statement is
basically a better behaviour changing ini setting and PHPs history is paved with those. I very much
hope for scalar type hinting, especially a strict variant but this is not what we should merge.
cu,
Lars
Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc
Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc