Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112859 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 34844 invoked from network); 13 Jan 2021 06:37:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Jan 2021 06:37:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E24341804A7 for ; Tue, 12 Jan 2021 22:15:11 -0800 (PST) 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,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-Virus: No X-Envelope-From: Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) (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 ; Tue, 12 Jan 2021 22:15:08 -0800 (PST) Received: by mail-vs1-f52.google.com with SMTP id u7so516026vsg.11 for ; Tue, 12 Jan 2021 22:15:08 -0800 (PST) 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=koFO9+HmoACNuPK87nm4ybFelpjjauK2vP84Rpnejkc=; b=bYnYMyfpn91Cj8OPa3YMafq037/wkT1fvd0+MAwAkW3UhRWNnqoDAm1c7hPZgvbZMC /vvm+J0/rV4HFbcqwIyqeZqG5HuXKfzco6WYLAOTscxNYviCrTQmA8hMICyO2qRtJrTM QM4Md5O6vuvVrqahqA3yyuMng7fs6JaoIvGddzuKWocrNGgH9WKUCSsRkcwRCCD1Y2Uv XmjYfDWs8ayc4sQhmJqCFtHwZEUiUWyyiCLTVy+ZAmacbKWEer/+pJnvLMemFoDDX6B8 C1T0WmvHAnuV6KdLfgzMaQHLRO5eT6X/fT9ygB3ny5P2xRqySz63PqjN8U4rCY7OdlqD C8mg== 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=koFO9+HmoACNuPK87nm4ybFelpjjauK2vP84Rpnejkc=; b=YeGrAlN/9xVoQkjUotkuEhP453j2k6SmCmRlg2WC57pw/yFpl2GPLo+j/OTueIViOj xz6McwJGuKxEgdf7DQ7s0U+ELQHYb8PF08jVBGaT9n73IkxuNNhxMnctn+0/hVhXN4jw 5xAht28fockJXBL2nsdSV/lN1p2JJ942b1aOVmibmeLnt9Qi2Qt7b8IxVLIUCO3e7+fo sF2jNCF3ssB86Oo8IPSThw0+ERpAlXEP/kvQUMr7yb+qj5YVHj2pHUHAmgEtK36XQsuI 1W8gwH+hGKe83e6v/+JZFqNCsKhfQa8qz+gUKSh79xJJQ12FXa1JbrI9rbyPWeFZo286 fjvQ== X-Gm-Message-State: AOAM531VKAen0YEUqoEe25PhfSftfZjC61fd/PsC+iq7g62iEu8Go7Jz Z1dUHWtgk2dmxnmSQYv99lxhJSRuaLr3xr9UJPI= X-Google-Smtp-Source: ABdhPJweW/4VlS01Us8oVYcGZr9f2+a/wl4mp29GZU5wSSz2JbTOMmQfBFumsE/H46y5UAlvdr+ky1ClrSEikuHCous= X-Received: by 2002:a67:6407:: with SMTP id y7mr594001vsb.23.1610518505907; Tue, 12 Jan 2021 22:15:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 13 Jan 2021 01:14:54 -0500 Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000072e9f805b8c20f94" Subject: Re: [PHP-DEV] [RFC] Allow object keys in arrays From: matthewmatthew@gmail.com (Matthew Brown) --00000000000072e9f805b8c20f94 Content-Type: text/plain; charset="UTF-8" This proposal is interesting, and I see why the enum proposal makes it useful. Supporting this will mean a small amount of work for me (assuming it passes) and other static analysis tools, but I don't want that to factor into anyone's decision. I am curious, though, whether the scope of this RFC could be narrowed to just allowing enum cases as keys? That might avoid issues with objects that cannot be cast to string. --00000000000072e9f805b8c20f94--