Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109798 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 17581 invoked from network); 23 Apr 2020 06:30:53 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Apr 2020 06:30:53 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 445C01804C2 for ; Wed, 22 Apr 2020 22:02:42 -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=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 22 Apr 2020 22:02:41 -0700 (PDT) Received: by mail-ua1-f42.google.com with SMTP id t8so4440859uap.3 for ; Wed, 22 Apr 2020 22:02:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FU5rmTXX20bqfphvkthD9qSQcBKTTy3z2vmDIB6jtEo=; b=RcLNsd8OWoCtP3koJfo0+y6cvoQ5ggnnpW6YuJLqHWR2Oo+XKyVvUb097tHpUdLe7f n8BjpwggId4JQbEzoYVq7atlVfDlrG4QM9Ts6detIdXxqMPPpn/mRs7AXVLxPYIkJJzk KhrPluWP5PqTf8ScZEXWyAWH7+mSHzzH9JS7KxUqDVmEfsvzJhGedmqb4d5MkRJtK3ff 8BcoIZ4oHu5Dqwvj2gMdUnVp3qUCs8c77ZrqfuZKQavnbKpcLncfUR5yd60NElYuiVAq 3nMpmQY6Hts6GxfwcdQy5b5RztrdNPfj/wIYN7xeaTXTLXwFhOCkXqPXPuaY5dUj+KxO mmoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FU5rmTXX20bqfphvkthD9qSQcBKTTy3z2vmDIB6jtEo=; b=OcM/4rCXCLpk3+ocCgfWR/ipHtP7g2AKeWwnxdMcxD4hiWRNR6irMa/UsXGigMsmbS Ucl2PCupF6QlgRjZrT24dDJr1CHnDZgd+eUOysK5Uq8Rq/QgSITMMHK1Xvb6G166KeuU LUBaQGBgPc5TEYTvZtIRsfYLWWpppspMBclPlhXARqG8mRJHWvIcBv5uxL9jtvFH9nac +FwKLOLR9KQbY+KRbmwcHGHrrXbQ6DdnRillMtnnhJMvANyp2JE96yhR6XCzPy5NB6Nm /tLkatMXnUBMHbZHO3AQPGFPrVzsci09Hp1u7WG9uaIiUH02c6WDQozZXBycBEwfWlTe EY/A== X-Gm-Message-State: AGi0PubwjXvdg4vWHq2E0mgqw+tDmRmRg3L1OymC12nHCr225th0rohJ LKvrLtYpSDRZXXVqfsBPr6rFflCCsRKTUeEYXxss/NUr X-Google-Smtp-Source: APiQypIfN80TdGsNodMhu9EaQyRu2D7kAUvmkJt66PE37J7xC9/Q4iUA3hS7ZdTkjCmH0G01R6KBvd416N4FOkOwPj0= X-Received: by 2002:a67:7382:: with SMTP id o124mr1840296vsc.153.1587618160095; Wed, 22 Apr 2020 22:02:40 -0700 (PDT) MIME-Version: 1.0 References: <4c1cd016-1e41-4ebc-afc4-d8d3cd1c319b@www.fastmail.com> <31441489-11c6-4d99-9c53-6ac0e877f268@www.fastmail.com> <73b33704-ded2-4cbc-93bd-17e8874177f2@www.fastmail.com> In-Reply-To: <73b33704-ded2-4cbc-93bd-17e8874177f2@www.fastmail.com> Date: Thu, 23 Apr 2020 01:02:29 -0400 Message-ID: To: Larry Garfield Cc: php internals Content-Type: multipart/alternative; boundary="00000000000078b6cb05a3ee28de" Subject: Re: [PHP-DEV] Any interest in a list type? From: matthewmatthew@gmail.com (Matthew Brown) --00000000000078b6cb05a3ee28de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > This is the *design* process for a language, and it's important... Stepping back to reconsider how collections work generally, and how we can improve them in a graceful way that leads to a clean end-state, would be very valuable. Though you have much more experience with internals than I do, I think that building a consensus around a bold new vision for PHP collections would be a near-Sisyphean task. Adding a list/vector type would be a much smaller, more easily definable task =E2=80=93 it was one of the first new types that Hack added, and by al= l accounts they're pretty happy with that decision. > Should we also be adding a dedicated dictionary type as well? Maybe? I think there'd be less to gain from a performance standpoint though, so I didn't want to lump that in with any list proposal and risk derailment. --00000000000078b6cb05a3ee28de--