Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107519
MIME-Version: 1.0
References: <CAF+90c-CaepNPOxOa937qCDwJ6c2XuQn0QKSk+-fH6wu9bSE1A@mail.gmail.com>
 <237dbf6e-cd91-4e6d-8c97-1fbbabcd9f21@www.fastmail.com>
In-Reply-To: <237dbf6e-cd91-4e6d-8c97-1fbbabcd9f21@www.fastmail.com>
Date: Fri, 11 Oct 2019 19:23:04 +0100
Message-ID: <CAAwbVucQ51EFvF89dUGw-qVKj7Qg8QWB4+fLrdrOkzx1L5SOJg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000943ff40594a69c5d"
Subject: Re: [PHP-DEV] Warning for "confusable" types
From: oludonsexy@gmail.com (Olumide Samson)

--000000000000943ff40594a69c5d
Content-Type: text/plain; charset="UTF-8"

On Fri, Oct 11, 2019, 6:47 PM Larry Garfield <larry@garfieldtech.com> wrote:

> On Fri, Oct 11, 2019, at 8:54 AM, Nikita Popov wrote:
> > Hi internals,
> >
> > Something I've seen play out a couple of times: Newbies try to use
> > something like "integer" or "resource" as a type, and then get a
> confusing
> > error message along the lines of "must be an instance of resource,
> resource
> > given".
> >
> > I would like to throw a compiler warning in this case, that looks as one
> of
> > the following:
> >
> > > Warning: "integer" will be interpreted as a class type. Did you mean
> > "int"? Use qualified name or "use" to suppress this warning
> >
> > > Warning: "resource" is not a supported builtin type and will be
> > interpreted as a class type. Use qualified name or "use" to suppress this
> > warning
> >
> > This warning only triggers if the type is lowercase (integer but not
> > Integer), is unqualified (integer but not \integer) and is not imported
> > (there is no "use integer"). This provides multiple ways to avoid the
> > warning for code that does legitimately want to use lowercase "integer"
> as
> > a class type.
> >
> > Implementation: https://github.com/php/php-src/pull/4815
> >
> > Thoughts?
> >
> > Nikita
>
> Can you clarify where exactly "compiler warning" would be displayed?  Is
> that an E_WARNING?  How would I as a user see a message when I write
>
> function foo(integer $a) { ... }
>
> --Larry Garfield
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php


As a warning I think, seems I've encountered those errors many times ago.

The solution Nikita propose is good, it doesn't deal with too much.

These errors are there already, only just giving it a properly meaningful
description.

+1 for the proposed description.

--000000000000943ff40594a69c5d--