Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108459
MIME-Version: 1.0
Date: Tue, 11 Feb 2020 12:13:54 +0100
Message-ID: <CAD5P3=JwFK03L-DWJYaa0dbBj1chbef_=K-vyawLNeoAz7dHjA@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000003936cf059e4af4bf"
Subject: [RFC]
From: manuelcanga@gmail.com (Manuel Canga)

--0000000000003936cf059e4af4bf
Content-Type: text/plain; charset="UTF-8"

Hi internals,
I Would like to present a possible new "::func resolution" for your
consideration.

In first place, PHP now support "::class" in this way:

use My\I18N;

$mapped_array = array_map([I18N::class, 'translate'], $array);
It avoid add Full I18N  namespace in callback.

However with functions is different:

use function \My\I18N\i18n_translate;

$mapped_array = array_map('\My\I18N\i18n_translate', $array);

What is the useful here of importing the function?.
My proposal is ":func" in order to avoid full namespace in callback of
functions. E.g:

use function \My\I18N\i18n_translate;

$mapped_array = array_map(i18n_translate::func, $array);

"<string>::func" should validate if a function with `<string>` is imported.
In this case, "<string>::func" is replaced with FQN of this function,
otherwise with only "<string>"

What is your opinion ? Do you see it useful ?

Thanks and I'm sorry for my English( I'm a Spanish ).

Regards

--0000000000003936cf059e4af4bf--