Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117550 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 62009 invoked from network); 20 Apr 2022 14:56:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Apr 2022 14:56:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id AC8341804D9 for ; Wed, 20 Apr 2022 09:30:25 -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_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-yw1-f174.google.com (mail-yw1-f174.google.com [209.85.128.174]) (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, 20 Apr 2022 09:30:25 -0700 (PDT) Received: by mail-yw1-f174.google.com with SMTP id 00721157ae682-2edbd522c21so23774907b3.13 for ; Wed, 20 Apr 2022 09:30:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CngQ62th+EO5ynrwCUv20z8Zn0u0bqgAM3GtgaZ40Xg=; b=WY6MLAvpPDBlzyDKHOhx/22+VhhYjDQ1wRaYlZ78q+CVTinkfZ5EoDkV70LH/0CxlP 7j9L1RiJHGFpnWlLPignTU592F5VUDOASzyC/x+lamHN82GOOWn3+S3ZwHOOhcGEEdsU Q07QZYaVksLGm7zk/expjG76i9j3rbdrrvKMG8OeQg4+37PvBCS71+UraoeVyNrwj4o4 eZr6cDqBaQZsbg9Hm9DOmTv7bypQcsni+mWcOzojA1UEVfp0IwLLn0bdXD3R2IiR3zWA 2mEy7HK9rqjcm7Q0Ds3jUvkgJYBOIz2/c+h4tXrM/3Y+KrRNw0Sik0IV9T6VgKO9UI94 9GYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CngQ62th+EO5ynrwCUv20z8Zn0u0bqgAM3GtgaZ40Xg=; b=SIuoLgERYWKlDgT6LodUE4diFlDGgiGebWeIpaHDL83m8KFEDc+wOPYEa85fRBfbWh CGvbyLAF2i38OZ7x0mOST2vINm6/Dd3dcmWdJl5yKD6zIG0b8Shap3wPEeiKZ+hCsBF2 7GxubRJBChoG4hoR/Az1b13b8ZoRQCfFyI3T58ANMNGaizgsL/09TsAELlm6WkLdSvV9 iiVyEtPuathxypFsYS0W7/oS6aYb1Uax/34LpOQ6aB7XsRclIURsP5rmtfB3yO03LTPL S38DO3oLMp3vn/PV1KyoigeRFafFeic7wTVnWIpK2xmpn+gHYPv609DGsPbs2R0WcZxR wrgg== X-Gm-Message-State: AOAM5324oBZ+UiwxHhSiyExI71qSjDKZmZLjEskzubZZueFK2Q8JcrQn NwpGumdgKNJ4FTXnl5DNXytlT8Nc1lvEj/koWq0= X-Google-Smtp-Source: ABdhPJy3RqzO7FJynYe7bJaQcDrZi3DTXCaPSY51GPrtrzBF47E6YjP9uFpk6HS8y10zVzdaV66ZTX6OwxpSQEmiqEo= X-Received: by 2002:a0d:eaca:0:b0:2ec:e40:52fa with SMTP id t193-20020a0deaca000000b002ec0e4052famr21575006ywe.458.1650472224718; Wed, 20 Apr 2022 09:30:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 20 Apr 2022 17:30:13 +0100 Message-ID: To: Andreas Hennings Cc: Sara Golemon , =?UTF-8?Q?Tim_D=C3=BCsterhus?= , PHP internals Content-Type: multipart/alternative; boundary="000000000000aa846a05dd1882e6" Subject: Re: [PHP-DEV] [RFC] Add true as type From: george.banyard@gmail.com ("G. P. B.") --000000000000aa846a05dd1882e6 Content-Type: text/plain; charset="UTF-8" Hello internals, I've expanded on the RFC: https://wiki.php.net/rfc/true-type Please let me know if there are still aspects which need clarification. I will also say that I think enums are far superior to literal types, but only having false and not true is extremely weird to me (and in a pure type theoretical perspective I would have preferred to not even have false). The complexity of the implementation is also "trivial" because the PHP engine already considers true and false to be two different ZVAL types, whereas a complete literal type implementation is going to be way more complex and I doubt be far from efficient. Best regards, George P. Banyard --000000000000aa846a05dd1882e6--