Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118792 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 60991 invoked from network); 11 Oct 2022 04:38:20 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Oct 2022 04:38:20 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E2D461804AC for ; Mon, 10 Oct 2022 21:38:19 -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,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-vk1-f171.google.com (mail-vk1-f171.google.com [209.85.221.171]) (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 ; Mon, 10 Oct 2022 21:38:19 -0700 (PDT) Received: by mail-vk1-f171.google.com with SMTP id g85so6106582vkf.10 for ; Mon, 10 Oct 2022 21:38:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dV6+L/17efT7eliuQwcmYtPiT0VeBLR0EgTNdb/gy/g=; b=gOZu+HJxnsWexWQfDopz/NnGTgJy5knIkm/KcTyMc7UB0Vmino4IDUA5QR1zdEzkki g8oIc0AUySo4+/68oiQemnkVEyMRUhXhuBql3AgRzj2L9BQT+AM9qEfFfAcWLvbqYGXe jlkVcNxdmt2Sm4S9YDWJ5QQSxwpcV52wDuBfm4EykrlfT+jAJ40pwV+SPb3B0e7RnbXJ VoUTlrX5QYk7ormNEbHhkgPgHzO/FNT0Bo0VXQEUN0MqFEz3pjHtGE4U3X2RdTH1HZzF THhZTcugopMSlipHFe5jgwA8TP+5ipwRrdWGPiHx4nK2sLohRnKt252TK/EIA/wLwaO3 q02g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dV6+L/17efT7eliuQwcmYtPiT0VeBLR0EgTNdb/gy/g=; b=vbBqXCo2GGsalMpNli+3qBQG27K4YpkElESz088+dDIBEROnES/vaBU6H75ZJAKfsb WGwlICNGmcOu/ouvaIHRuhRopdKZ50S0a5ygkeyBSwGjsrBl+h5BNnTFGugj8hoLmyFj 7lB39yfRWEC6KLfv96vqrITgf5f6Kvn+OqbqQ/kbQByCG6HgGTy/HeUQXLgc+laYyplR 09mLgN577BXaD3C1om/bcUTSK00V40g4+/NFxtnwnbW9uf1AuJcvtey0BG7lhi72EXg0 wb0XZ1g3/94QjwOl8dgAditB7j7320iZ6bMVMwWQ3N9MmJWA6L/7DxnHLXLCUcyVMS0k yeMg== X-Gm-Message-State: ACrzQf2Xm+qboPykARrB9hrMZPQUdr6arH3wM/azbp0tXGt6vop/zse+ Ifiy7gRiEr+6qYxHYh+NZZBAa2jfYuROldRr8oo= X-Google-Smtp-Source: AMsMyM65kCjYIilL0vfKX1/y79xnvSyAh++1lP8vscWQ3IfMDF06ZgMNTsPK6RdhZQ+MhKZ/2ThREQmldy6h0Ila8Bg= X-Received: by 2002:a1f:988c:0:b0:3aa:cf0a:e0f7 with SMTP id a134-20020a1f988c000000b003aacf0ae0f7mr10386141vke.24.1665463098415; Mon, 10 Oct 2022 21:38:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 10 Oct 2022 21:38:05 -0700 Message-ID: To: David Gebler Cc: David Rodrigues , PHP Internals Content-Type: multipart/alternative; boundary="0000000000005e1f5605eabad893" Subject: Re: [PHP-DEV] Experimental features From: jordan.ledoux@gmail.com (Jordan LeDoux) --0000000000005e1f5605eabad893 Content-Type: text/plain; charset="UTF-8" On Mon, Oct 10, 2022 at 5:05 PM David Gebler wrote: > On Tue, Oct 11, 2022 at 12:05 AM David Rodrigues > wrote: > > > The idea is that the experimental features are exclusively something that > > the PHP team has voted for (approved) and that will be part of the > language. > > > > So they're not experimental features, they're accepted RFCs, maybe with a > lower voting threshold. > > I don't really see what the confusion is about. It's for features that we have all agreed to include, but that the public API or behavior might change in minor versions while usage information, feedback, and so-on happens. The idea behind an experimental inclusion would be something like "the concept behind this feature we've agreed to include, unless something truly drastic comes up once it's out in the wild, but the syntax, parameters, and signatures might change while we look at usage and real-world code. It's like the opposite of a Deprecation notice in my mind... it's a flag on specific code that lets people know *ahead of time* that BC breaks in a minor version might be necessary for this feature for a little while. Jordan --0000000000005e1f5605eabad893--