Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111803
X-MailCleaner-return_path: brendt@stitcher.io
X-MailCleaner-sender_address: brendt@stitcher.io
X-MailCleaner-recipients: internals@lists.php.net
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A7CA3C61-A38A-4002-BA07-F47102238D15"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 3 Sep 2020 09:38:45 +0200
References: <89FF9360-609A-439F-BDBE-B3B4C141E00F@newclarity.net>
 <95eddd89-9915-14fc-7649-9de0e8dd349d@gmail.com>
 <BF889FDF-AFCC-4122-A139-AB06C7C6F3CC@newclarity.net>
 <306f190e-efd8-0db8-a9c3-aff3c90aa1c6@gmail.com>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <306f190e-efd8-0db8-a9c3-aff3c90aa1c6@gmail.com>
Message-ID: <53FF7328-F05C-496E-8F57-5A81B899CED1@stitcher.io>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-MailCleaner-TrustedIPs: Ok
Subject: Re: [PHP-DEV] Draft RFC: foreach iteration of keys without values
From: brendt@stitcher.io (Brent Roose)

--Apple-Mail=_A7CA3C61-A38A-4002-BA07-F47102238D15
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all

I want to point out the use-case when you're using CS tools, static =
analysers and IDEs: they report unused variables as errors. There are =
ways around those errors, but it's more convenient if there's language =
support. I'd say that conceptually it's also more correct: if you're not =
using a variable, it shouldn't be there.

As some of you have shown, there are ways achieve the same result =
without adding new syntax. Just like we didn't need short closures and =
keep using the normal closure syntax, like we could write if statements =
and didn't need the nullsafe operator, like we didn't need named =
arguments or constructor property promotion. I think the past years of =
PHP devlopment have shown that the majority likes convenient langague =
syntax and constructs, not because it's absolutely necessary, but =
because it's just a little more clean, a little less verbose, a bit more =
convenient.

PHP has been maturing over the last years, which means there's room, and =
need, for things that aren't strictly necessary.

Kind regards
Brent

> On 3 Sep 2020, at 09:18, Stanislav Malyshev <smalyshev@gmail.com> =
wrote:
>=20
> Hi!
>=20
>> If it adds a micro-optimization, great, but allowing a developer to
>> explicitly signal intent is the primary argument for adding void.
>> IMO.
>=20
> You can signal intent by using $_ or $dummy or whatever. You don't =
need
> new language construct each time for each way of using or not using a
> variable.
>=20
> --=20
> Stas Malyshev
> smalyshev@gmail.com
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>=20


--Apple-Mail=_A7CA3C61-A38A-4002-BA07-F47102238D15--