Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121318
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 31940 invoked from network); 15 Oct 2023 02:42:50 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 15 Oct 2023 02:42:50 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id D48861804AC
	for <internals@lists.php.net>; Sat, 14 Oct 2023 19:42:49 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS9370 160.16.128.0/17
X-Spam-Virus: No
X-Envelope-From: <saki@sakiot.com>
Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Sat, 14 Oct 2023 19:42:48 -0700 (PDT)
Received: from smtpclient.apple (56.153.159.133.rev.vmobile.jp [133.159.153.56])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id 3B3ED401D4;
	Sun, 15 Oct 2023 11:42:45 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1697337765;
	bh=4zcHe7pchO/lXg8ml7HX2OW3bD3pcOKNck8DLfZicXA=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To:From;
	b=QVW3ONNGrqexSGFj8gFC/DCKQ//yH36L1aMObW8Zkod+0/R9rEPMzC2Ppqzq2z1nB
	 jyTVJ1fcfKGAj1014jNMHoZ1zIP30AdlSA4/p+lAFjaEhfKvwD2NHAfekVZ1bcNYcg
	 8lOhjSDQZoHyCOGjQwUJVypZHtpGvn5pobAE525M=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sun, 15 Oct 2023 11:42:32 +0900
Message-ID: <3006DBD0-411C-4855-A101-9B8861544B61@sakiot.com>
References: <CAL-Ucw5Yu4ai-n6t=GdRX+DC+8a7_Z5Mw-pYN+jUtpZUGN7svg@mail.gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <CAL-Ucw5Yu4ai-n6t=GdRX+DC+8a7_Z5Mw-pYN+jUtpZUGN7svg@mail.gmail.com>
To: David Grudl <david@grudl.com>
X-Mailer: iPhone Mail (20G81)
Subject: Re: [PHP-DEV] Two new functions array_first() and array_last()
From: saki@sakiot.com (Saki Takamachi)

Hi, David

Many times I've seen reset() used to meet this requirement.

I support this, not only from a side effect standpoint, but also from a read=
ability standpoint. I would also like to add the opinion that it is better b=
ecause it is simpler than the function name in the original RFC that is bein=
g referenced.

Best regards.

Saki=