Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108242
MIME-Version: 1.0
References: <CAKtGGAsh-38W1UjgDaoQFzhKNOqTy3QGV8fE1-6-PPob2zw6Vw@mail.gmail.com>
 <CAF+90c8yAqHeLRzeX0sYxnQ30JAtg=Ubp7sDyonCkS5V7goN5A@mail.gmail.com>
 <5DC86728-1BBF-4DCA-8A6B-9B0B190DB99D@newclarity.net> <CACXBjuhpy3b0fpKHqtDbWDiwVSruRa_NgNUaLOQrduKY-WAx3g@mail.gmail.com>
 <3091DC6D-E03B-4AF5-8DC6-F3B2772956BD@newclarity.net> <5d1eaf45-d888-3fe6-7c40-02b0c8c81b61@gmail.com>
 <FC578397-3F03-4E4C-B531-FCFE9CC55447@newclarity.net> <cf84d92d-8e7a-de26-9d08-7d2ac6f9184b@gmail.com>
In-Reply-To: <cf84d92d-8e7a-de26-9d08-7d2ac6f9184b@gmail.com>
Date: Sat, 25 Jan 2020 16:19:05 +0100
Message-ID: <CAFLRTJ-fAS1ookm26QL-bgSMwdGuCt-RPQBmOD97VoXeVmhNDg@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c6120a059cf86539"
Subject: Re: [PHP-DEV] Typed array properties V2
From: mtkocak@gmail.com (=?UTF-8?Q?Midori_Ko=C3=A7ak?=)

--000000000000c6120a059cf86539
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Given this orientation, can we also have this debated once more?

https://wiki.php.net/rfc/callable-types

Right now, I am using 7.4.2 in production and in my next book and I cannot
explain how it feels good to have those types but along with the loosely
typed freedom. That's the killer advantage of PHP and IMHO version 8 will
be quite popular due to the 7.4;



On Sat, 25 Jan 2020 at 16:12, Rowan Tommins <rowan.collins@gmail.com> wrote=
:

> On 25/01/2020 00:12, Mike Schinkel wrote:
>
> > So saying "use a static analyzer" is IMO just pointing out an overall
> > weakness that PHP can't automatically do static analysis on its own.
>
> I'd just like to repeat that you and Rasmus are in agreement here. He
> didn't say "PHP doesn't need to change because static analyzers exist",
> he said:
>
>  > it would be amazing to have a static analyzer built into PHP
>  > ... but that is a huge task and goes way beyond just this particular
> check.
>
> Choosing whether that analysis runs automatically during server startup,
> or as a separate command-line script, is just one detail among many. It
> probably wouldn't make much difference to the rest of the analysis code,
> and it might even make sense for it to support both modes. For instance,
> it might be optional for command-line scripts, so you could have options
> for "analyse and run", "run only", and "analyse only".
>
>
>  > One of the main strengths of PHP =E2=80=94 and IMO one of the reasons =
for its
> incredibly marketshare =E2=80=94 is the ease with which PHP code can be w=
ritten,
> tested, and deployed.
>  > And that ease translated to ubiquity.
>  > Adding a recommended build step to that in order to gain correctness
> weakens that value proposition and threatens future ubiquity as other
> language improve.
>
> Yes, the convenience of having something run automatically is definitely
> worth considering, as long as it doesn't introduce new delays and rules
> that get in people's way.
>
> It partly depends what kind of checks were being done, I guess, and
> therefore how much time it would take to run, and how much of a project
> it would need to analyse at once.
>
> Regards,
>
> --
> Rowan Tommins (n=C3=A9 Collins)
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--000000000000c6120a059cf86539--