Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111795
To: Nikita Popov <nikita.ppv@gmail.com>, Mike Schinkel <mike@newclarity.net>
Cc: John Bafford <jbafford@zort.net>, PHP internals <internals@lists.php.net>
References: <89FF9360-609A-439F-BDBE-B3B4C141E00F@newclarity.net>
 <CAF+90c8A7oWmM45poXj2goghCa00Jz3fiU7ud-aZgVwCfgXOzQ@mail.gmail.com>
 <a74ead4b-868e-8d85-9850-72fcdebc3cd9@gmail.com>
Message-ID: <7adfa9fc-3b20-5171-62b6-4c4df57fbe72@gmail.com>
Date: Wed, 2 Sep 2020 21:53:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <a74ead4b-868e-8d85-9850-72fcdebc3cd9@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Draft RFC: foreach iteration of keys without values
From: dik.takken@gmail.com (Dik Takken)

On 02-09-2020 21:31, Dik Takken wrote:
> Even if we decide that it is not worth the trouble for foreach loops,
> there are other cases where this new syntax can work well. Array
> destructuring has already been mentioned.

Replying to myself: It just occurred to me that array destructuring
already allows omitting values:

  [, , $username] = getUserData();

I still do find using void here more clear though, more intentional.

> Another case is the one where a function intentionally does not use one
> of the arguments passed to it. This happens easily when using callbacks
> or when implementing interfaces. A function declaration could look like
> this:
> 
>   function foo($arg, void) {}
> 

Given the array destructuring syntax, an alternative syntax might be:

  function foo($arg,)

Again, I would prefer to see void here in stead of a trailing comma. In
function calls a trailing comma is already allowed and it has a
completely different meaning, which can be confusing.

Regards,
Dik Takken