Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118773 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 66926 invoked from network); 6 Oct 2022 21:38:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Oct 2022 21:38:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 860CB180539 for ; Thu, 6 Oct 2022 14:38:38 -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-vs1-f46.google.com (mail-vs1-f46.google.com [209.85.217.46]) (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 ; Thu, 6 Oct 2022 14:38:38 -0700 (PDT) Received: by mail-vs1-f46.google.com with SMTP id 126so3295089vsi.10 for ; Thu, 06 Oct 2022 14:38:38 -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=N2FP3Q3GheIWfH0FSt6rfiQHnd5rNxNl8Rm0Ok+Wg7A=; b=DluQtPfPoilpdmk1lZ9PQaNxUDmYvtv35PeEfNGVxt8T8sh1RuxGKEb64e1GJjfvRT gQ1MXO1EeFTbNih9JfZklYZyqyvxUP5Vt7PRw6DXxZNpwBBaioadCcG3bxYnWdWUQZms hXXk5S6EjC4GbM+1rPs3k5/IX8gqA5lmEKNJihJ6rDVbCJWpmmP6T1YZVJMYcak/QnYO zsPtgmfuJbJj2GCLmFAG6MyXuxiTobQM41CS5i/QtnzJKfKRQV/A3x7dkt8zVbNH/Gja 81HGujUYtDtzWgsnIALQtwX/ldGcPGD+rgsaTrWM4++R31f8CCFg20RFDoLIGM8UnEil YThQ== 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=N2FP3Q3GheIWfH0FSt6rfiQHnd5rNxNl8Rm0Ok+Wg7A=; b=NijoUyAspofLahnLeBzatsdiNxISMEHYUPLBCdeiqt32FgqVuw1tLNC09zdnte7N0H IC00Z5qLO0AZio0kQFA+jE+KA/31Awm3bt1y2a7E2o+xqz1O2ZTv0663fHenWoHAMTQZ s7X34mMKQslg0etw9l983/JfenVlFfYEabNADnEgUubaT0kFw126te3YxbEXuxNEBx9B IxZCcw9RXNZ+L+zrBkWpwrT+5mecepqlzOWwD+LXpU4LuQiXWZc4wVcFgjAjlb8GFFdJ a8//K9CMfmq+gCcF61O9Q9JdarKNjIvQ8KhpKpqEeNnY69g4ZAa73uwMv7Yc2PNp+cPB YO+A== X-Gm-Message-State: ACrzQf1R8Q6ohpkqAltflPs4STsen4T9T4JwAJQ0wyWsjvvf9iyxvSHC 4psDEGPtytzdJ7t80tU97NMY3TXcGdhKI+/rzYx055nl X-Google-Smtp-Source: AMsMyM7/s1fBS57qqK+Hu9FbNBKfVvPVGp4RZsmS4yYori85RJ8FarCYWRvAs0CCAgMuvpwbQ9KQrhCJkhXJNWwhO64= X-Received: by 2002:a67:f943:0:b0:3a5:662a:b600 with SMTP id u3-20020a67f943000000b003a5662ab600mr1022148vsq.84.1665092317294; Thu, 06 Oct 2022 14:38:37 -0700 (PDT) MIME-Version: 1.0 References: <1aa20877-3365-0ace-25d2-1cb1be8f3bcc@gmail.com> <55686BD4-4C67-4A4F-8BE4-BDF0149296FB@gmail.com> In-Reply-To: Date: Thu, 6 Oct 2022 14:38:22 -0700 Message-ID: To: Rowan Tommins Cc: PHP Internals Content-Type: multipart/alternative; boundary="00000000000017355905ea64844e" Subject: Re: [PHP-DEV] Experimental features From: jordan.ledoux@gmail.com (Jordan LeDoux) --00000000000017355905ea64844e Content-Type: text/plain; charset="UTF-8" On Thu, Oct 6, 2022 at 1:12 PM Rowan Tommins wrote: > On 06/10/2022 17:41, Alex Wells wrote: > > For example, Kotlin has recently introduced a new feature - unsigned > integer types. > > > I'm still struggling to understand what I, as a user, would do about this. > > If I start coding an application that relies on these new types, is > there a chance that they'll be removed completely, and I have to rewrite > it all? Is there a chance that every minor version I upgrade might > introduce subtle changes in the behaviour of my code? Or is there just a > chance that someone will decide the bikeshed's the wrong colour and I > have to regex replace all my "123u" to say "u123" instead? > > I would think all of the above, though I would expect given the nature of the RFC process that it would be exceedingly rare in PHP. It would be like a release preview only in a stable version. It does seem like it would have utility in PHP, since we could introduce a feature without worrying about BC breaks if it needs to be modified and adjusted. Jordan --00000000000017355905ea64844e--