Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105494 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 58599 invoked from network); 29 Apr 2019 09:23:08 -0000 Received: from unknown (HELO mail-vk1-f169.google.com) (209.85.221.169) by pb1.pair.com with SMTP; 29 Apr 2019 09:23:08 -0000 Received: by mail-vk1-f169.google.com with SMTP id g18so2037042vki.10 for ; Sun, 28 Apr 2019 23:24:58 -0700 (PDT) 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:reply-to :from:date:message-id:subject:to:cc; bh=m6k031SHfqCNqAU6An753prrtPhikOgMjFBHbCxzJyM=; b=qyA6mc1VYhb6VxGpuvLQYvAVU9OGyTfnn3ByIDYDVcemqdxfGVZ1lVXliTJo6bdMLE NsqapsU08JoJGfsJKISbztxmXgfvppg4qEbWqJPZtUcSfM30vSdzmPtFDhZfivANBjN4 K7hYlK18G6r+SjxhRRmiWedbf3+VAy6UmK8mQ5VTuLXwUrtp80hPkyCbLp4JPbVLsElq AKoj2sByJeNv5JEfeG04DH2GxScA/hE6BeJW9ZqrKhZ3qtrI87dabZfdsIKUVUKgpDje C7u9V3+SYOF2wMrNznkt8be7sM7Z/nWIAJr6pHbVW0JtEiu1NVPgFtIS7HlX0Lv1ijmk t5CQ== X-Gm-Message-State: APjAAAUxTNrNyN9bFl4UTCJJBknLL9qM1Z+AkCGtGAscy9s9c6p3Ew3T 9gIn7wv79LZt3DQrO3DXw03fZz5Viplbws7p2no= X-Google-Smtp-Source: APXvYqxlcjvqRcsvPHp+f/Jg0k9KVBsAGNAr5UG+GF50I8FAtXAIYsTG9q287BJ0foD7jK/bafwZEbBBY6gbxJ6lqjI= X-Received: by 2002:a1f:29d0:: with SMTP id p199mr7470000vkp.30.1556519097820; Sun, 28 Apr 2019 23:24:57 -0700 (PDT) MIME-Version: 1.0 References: <7b3a754e-3225-1921-b751-d1dec0435daf@gmail.com> In-Reply-To: <7b3a754e-3225-1921-b751-d1dec0435daf@gmail.com> Reply-To: bishop@php.net Date: Mon, 29 Apr 2019 02:24:32 -0400 Message-ID: To: Stanislav Malyshev Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000e969f60587a55783" Subject: Re: [PHP-DEV] [RFC] Change the precedence of the concatenation operator From: bishop@php.net (Bishop Bettini) --000000000000e969f60587a55783 Content-Type: text/plain; charset="UTF-8" On Sun, Apr 28, 2019 at 9:45 PM Stanislav Malyshev wrote: > > > Nikita, impressive leg work; thanks. It validates Bob's intuition from > the > > RFC ("... these occurrences are quite rare as it almost always is an > error > > in the current form, rendering the impact minimal.") > > If the impact is minimal, why do it at all? So, at the cost of BC break > and breaking old code (which is most definitely not in composer packages > and likely isn't publicly accessible) we maybe fix 5 bugs. Does this > justify a BC break? I don't think so. I really wish we'd stop trying to > add a thousand small incompatibilities between PHP 7 and PHP 8. > Because when the language becomes more obvious and intuitive, our users benefit. Code that appears to produce a particular result actually produces that result. No WTF trap for users to fall into. No questions sent to mailing lists or SO asking "why", and no documentation written to explain away that why. Because there simply isn't a why; it's just the way it is. No justification suffices. We have the opportunity to exchange the way it is, for the way it should have been. I think we should accept that opportunity. --000000000000e969f60587a55783--