Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111755
To: =?iso-8859-1?Q?Riikka_Kalliom=E4ki?= <riikka.kalliomaki@riimu.net>, PHP
 internals <internals@lists.php.net>
Thread-Topic: [PHP-DEV] Request for couple memory optimized array improvements
Thread-Index: AQHWf8J/IUqAAtE5mEGZSPifY1zUKqlS2ZYI
Date: Mon, 31 Aug 2020 23:21:38 +0000
Message-ID:
 <DM6PR07MB66182F64E77921B452875473F9510@DM6PR07MB6618.namprd07.prod.outlook.com>
References:
 <CA++kX6_Jd+mTeOdAe3UasAv5ZS-8xbUkjSNOj-LDgKryA4hqeA@mail.gmail.com>
In-Reply-To:
 <CA++kX6_Jd+mTeOdAe3UasAv5ZS-8xbUkjSNOj-LDgKryA4hqeA@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [MCHIldFs8zcP0OB4bCG2P4ki+Xvi89v1nUCE7S+TMwinGP5hMUxxn33kQRQ1lMYX]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 68e4f79b-c336-403b-fce6-08d84e049c93
x-ms-traffictypediagnostic: BN8NAM11HT197:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 PLSiQFMwLMC+rMTJwyD43RwjV0Qf3vfMTCnEPQSBWf+z7PELuE5vMYgdn5Dnc5xlIV3YpyV6yeAYvSs+pZU4ITIWqWllIXewsLYLVL7WR8i/0N1neMcsipBT8OPozSYUOWlQ3iO1q/y0tHwyHmz8QtM73xRf0qxFldJj2nul2Zu8ounXXkmfUZuC0t2sRz/5QlSyphVrsTBn3IrIcLqO7nJYyhKJZTHI/sNctd7ClP1BJT5mV/QogU9zNFKxSkX2
x-ms-exchange-antispam-messagedata:
 LIKNFDP+tiCmbzF9BIlX1M/lksCkIsDC8CtRymzMmXUqKV9DNtWiJ/wOhlv9E7hxwhFqjx5TELdoITovtGDPD7tU53+AZ+5fm2FLxNSXfiwVMiUILLc3MJwwYjfzDZI5GbQvFfbJvIG0/wOKlrOTNQ1wzoM3xwgCjNSgCha+uQXgDTErj7gxXSyAN8mauytgzl8lHrjuE7FdNrVHCEQELA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: BN8NAM11FT054.eop-nam11.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 68e4f79b-c336-403b-fce6-08d84e049c93
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Aug 2020 23:21:38.6065
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8NAM11HT197
Subject: Re: [PHP-DEV] Request for couple memory optimized array improvements
From: tysonandre775@hotmail.com (tyson andre)

Hi Riikka Kalliom=E4ki,=0A=
=0A=
> Another similar problem with creating array copies is the detection of=0A=
> "indexed" arrays (as opposed to associative arrays). Particularly when=0A=
> dealing with JSON, it's a common need to detect if an array has keys=0A=
> from 0 to n-1 and in that order. My understanding is that at least in=0A=
> some cases this would be trivial and fast to tell internally in PHP,=0A=
> but the functionality is not exposed to userland.=0A=
> =0A=
> Current common practices include for example:=0A=
> =0A=
> array_keys($array) =3D=3D=3D range(0, count($array) - 1)=0A=
> =0A=
> Memory optimized way of dealing with this is via foreach, but it's=0A=
> quite cumbersome and again, you must not use array_keys in the=0A=
> foreach. The following example demonstrates that the worst case=0A=
> scenario triples the memory usage using range: https://3v4l.org/FiWdk=0A=
=0A=
This was brought up in https://externals.io/message/109760#109795=0A=
there's a PR against php-src but there was some discussion about=0A=
whether php should strive to add an actual "list" type instead=0A=
and what it should be named - https://github.com/php/php-src/pull/4886=0A=
=0A=
I'm fairly certain is_list() would have to go through the RFC process given=
=0A=
the proposals for alternate approaches or alternate names=0A=
=0A=
Cheers,=0A=
- Tyson=