Hello internals,
The RFC has been accepted unanimously in favour with 38 votes.
Best regards,
George P. Banyard
On Thu, 17 Mar 2022 at 15:54, Levi Morrison
wrote:
> On Sat, Mar 12, 2022 at 10:32 AM G. P. B.
> wrote:
> >
> > I've started voting for the Allow null and false as stand-alone types
> RFC:
> > https://wiki.php.net/rfc/null-false-standalone-types
> >
> > Voting will last for 2 weeks until 26th
On Sat, Mar 12, 2022 at 10:32 AM G. P. B. wrote:
>
> I've started voting for the Allow null and false as stand-alone types RFC:
> https://wiki.php.net/rfc/null-false-standalone-types
>
> Voting will last for 2 weeks until 26th of March.
>
> Best regards,
>
> George P. Banyard
Hello,
I have
On 15 March 2022 15:41:45 GMT, "Côme Chilliet" wrote:
>Le samedi 12 mars 2022, 19:30:00 CET G. P. B. a écrit :
>> true is not a type in PHP compared to false, therefore it is not included.
>> I'm working on a proposal to add true as a type to PHP, but that's a
>> seperate RFC and discussion.
>
Le samedi 12 mars 2022, 19:30:00 CET G. P. B. a écrit :
> true is not a type in PHP compared to false, therefore it is not included.
> I'm working on a proposal to add true as a type to PHP, but that's a
> seperate RFC and discussion.
Was there ever an RFC for adding literal values to the type
On Sat, 12 Mar 2022 at 18:18, David Rodrigues
wrote:
> Maybe I'm a little late to this discussion, but is there any reason why
> *false|null* is allowed but *true|null* is not?
>
> I can think of few cases where *true|null* could be interesting, but I've
> been through situations like this.
>
Maybe I'm a little late to this discussion, but is there any reason why
*false|null* is allowed but *true|null* is not?
I can think of few cases where *true|null* could be interesting, but I've
been through situations like this.
Atenciosamente,
David Rodrigues
Em sáb., 12 de mar. de 2022 às
I've started voting for the Allow null and false as stand-alone types RFC:
https://wiki.php.net/rfc/null-false-standalone-types
Voting will last for 2 weeks until 26th of March.
Best regards,
George P. Banyard
