Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106058 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 6154 invoked from network); 26 Jun 2019 00:16:33 -0000 Received: from unknown (HELO mail-vk1-f169.google.com) (209.85.221.169) by pb1.pair.com with SMTP; 26 Jun 2019 00:16:33 -0000 Received: by mail-vk1-f169.google.com with SMTP id f68so3181vkf.5 for ; Tue, 25 Jun 2019 14:32:48 -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=DS4ow8Hp1xZ7BYP3XnqusRFbaNb714Og0wKi5WyAk/o=; b=SiestLTc2phA5GrNspeghvDY/iFURpYsT2UpJILx84CERW3vg80zkeaLwd/KkKrzrG aWvh8NbvlGP1SOKycjAh1rIUZVypTY/r0xOy6y6GRdFXgxWlDv1eaIC3LkA+A+Rxvd7s ARIJ4E7WAElo60ofclD/bk8hh0G6QdFyVuTPYTbwdbyGGTP1ssNdfBC7kNbBrV3Tt05W h5eN+zirXcfjCy8c931x7mhL7m0v1gmF8qfgcQeI5eop0dTUAEdenLcK9y+Gwto+fWGZ N/nDa8sojvoGziHCwUgxYl4WqOjlSkSmN8qvCIEtFRolxbrOL+6CmluTRcnGGsrWp/GW fgQQ== 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=DS4ow8Hp1xZ7BYP3XnqusRFbaNb714Og0wKi5WyAk/o=; b=qxNhBFN7mj/dbCnKEsaRuIJ8fkES8izOE8irfYiSiPN5wgeZnGkneIEoJcoH3jtgB9 XfrjwF5bSNyiuLZvnRyK61muPqgRN97cUXvX8kcNHnAPlyIUmuxh9sj0ftQh+UTcxLon BDnmSXh5TzJ7bi79zZ56uYU0YQ9nkB/8QFW8VWvyBDqyQRLSja/E/TZwBsQbAEWo706R y2mcygK218LXitgVmL7nmGCV1W06rD6qOxarmXz+H+ZxpmuPkEUVMgaj59bgAkyshpNf zMWXgwWd8dduVv9dVA4y5dass/jmSyPr8HqyxAAmoEeW0QU87lxeiGk8xDDCYJ1x/Wbn KzIQ== X-Gm-Message-State: APjAAAW6YwZmH5Jh6q1rLXevqGYTlcJKjsG9cDYq0Og9+tM0FmJrUmqp fy4RJK6y5AP+Wz2IZwBjCAVVpo+03QhnWu7WJEY= X-Google-Smtp-Source: APXvYqwTNe2MAJTdO5FJY2Pl/jD9+pqRYuqey64GT64AG0GEF6dkNC5H2d3I0VTkgJvlZXea0ybg+pvttWjdXtKl9xM= X-Received: by 2002:a1f:3692:: with SMTP id d140mr17772099vka.88.1561498367743; Tue, 25 Jun 2019 14:32:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 25 Jun 2019 23:32:37 +0200 Message-ID: To: Benjamin Morel Cc: Arnold Daniels , Guilliam Xavier , PHP Internals Content-Type: multipart/alternative; boundary="00000000000086dc6e058c2cab1a" Subject: Re: [PHP-DEV] [RFC] Strict operators directive From: krakjoe@gmail.com (Joe Watkins) --00000000000086dc6e058c2cab1a Content-Type: text/plain; charset="UTF-8" Evening, There doesn't seem to be a patch or implementation. Aside from the proposed semantics, which I can't really read because the document is malformed, the most important questions for me are: How is this going to work? Can it be done without significant complexity in the compiler or VM? Without an implementation I can't really consider the ideas proposed, because they are just ideas without proof that they are reasonably implementable. While you can technically move forward with an RFC without implementation, in this case the implementation should inform our decision at vote time. Cheers Joe On Tue, 25 Jun 2019, 23:19 Benjamin Morel, wrote: > Impressive work indeed, this would be a perfect addition to strict_types > that would remove a lot of WTFs while preserving BC with older code. > > Please note that the formatting of the RFC is broken after the Bitwise > Operators section. > > Ben > --00000000000086dc6e058c2cab1a--