Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108203
MIME-Version: 1.0
Date: Mon, 20 Jan 2020 14:58:06 +0100
Message-ID: <CAG9XoMTUCYdZyGXDR+gVEQDcnfL_z_XNiZ=ztwybSN0jVNG2Sg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fd694e059c92ae34"
Subject: WeakMap vs PECL WeakMap
From: benjamin.morel@gmail.com (Benjamin Morel)

--000000000000fd694e059c92ae34
Content-Type: text/plain; charset="UTF-8"

Hi Internals,

A year ago, when WeakRef was being proposed, some objections
<https://externals.io/message/104014#104068> related to the PECL Weakref
package <https://www.php.net/manual/fr/book.weakref.php> had lead the RFC
author, Joe Watkins, to rename WeakRef to WeakReference to avoid conflicts.

However, the latest addition from Nikita Popov, WeakMap
<https://wiki.php.net/rfc/weak_maps>, did not take the same argument into
account, therefore conflicting with PECL WeakMap
<https://www.php.net/manual/fr/class.weakmap.php>.

*First of all, how will this be handled in the docs?*

Now that we have a conflict on WeakMap anyway, and now that the PECL
package has been deprecated, and provided that the conflict can be
gracefully handled in the docs, *is there anything that prevents
WeakReference from being called WeakRef?*

Could we have both names in PHP 8, like WeakReference being an alias for
WeakRef?

Thank you,
Benjamin

--000000000000fd694e059c92ae34--