The `strict_types` directive is limited to applying strict type checking,
throwing a TypeError instead of doing implicit type casting.
The strict operators RFC is trying to do the same. Unfortunately there are a
view of cases where this isn't easily possible and the statement will have a
differ
On Sat, Aug 10, 2019 at 6:21 PM guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
> 1- How would you envision a shared runtime between PHP and P++, in the
> case that this new evolved solution decides to support objects as keys
> in array structure? This fundamentally changes internals
On Sat, Aug 10, 2019 at 12:37 PM Andrea Faulds wrote:
> Hi Zeev,
>
> As the person who initially proposed and implemented strict_types, I
> think this is heading in the wrong direction. Perhaps that directive was
> a mistake, if it will lead to so many attempts inspired by it to
> fragment the la
On 10/08/2019 17:08, Christian Schneider wrote:
There is a very vocal minority right now asking for BC breaking language
changes who IMHO are a bit too quick dismissing opinions of very distinguished
PHP developers.
I would just question the assertion that it's a vocal minority when
viewed i
Am 10.08.2019 um 17:04 schrieb Rasmus Lerdorf :
> On Sat, Aug 10, 2019 at 5:37 AM Andrea Faulds wrote:
>
>> As the person who initially proposed and implemented strict_types, I
>> think this is heading in the wrong direction. Perhaps that directive was
>> a mistake, if it will lead to so many att
Hi all,
I tried as much as I could to stay away from this discussion. My
personal take is that breaking the language in two is a *really bad
idea* (shouldn't I have put caps here instead?).
Anyway, people are commenting a lot on features that adds a feature to
the language, but nothing was being s
On Sat, Aug 10, 2019 at 5:37 AM Andrea Faulds wrote:
> As the person who initially proposed and implemented strict_types, I
> think this is heading in the wrong direction. Perhaps that directive was
> a mistake, if it will lead to so many attempts inspired by it to
> fragment the language, includ
Hi Zeev,
As the person who initially proposed and implemented strict_types, I
think this is heading in the wrong direction. Perhaps that directive was
a mistake, if it will lead to so many attempts inspired by it to
fragment the language, including this one. Personally, I don't actually
want
On Fri, Aug 9, 2019 at 4:30 PM Zeev Suraski wrote:
> In the spirit of my response to Bob, I added a new FAQ: "How does this
> differ from Nikita's Editions idea?"
>
>
"""Related to rollout - the Editions approach doesn't allow for just two
dialects - but any number of dialects. We could have a P
On Fri, Aug 9, 2019 at 11:27 PM Mark Randall wrote:
> On 09/08/2019 20:54, Zeev Suraski wrote:
> > It's available here: https://wiki.php.net/pplusplus/faq
>
> I am now even more confused.
>
> How is this drastically different to Nikita's suggestion of setting a
> compiler version via rust-like v
On 09/08/2019 20:54, Zeev Suraski wrote:
It's available here: https://wiki.php.net/pplusplus/faq
I am now even more confused.
How is this drastically different to Nikita's suggestion of setting a
compiler version via rust-like version declares?
It seems to me that it's just moving the vers
11 matches
Mail list logo
