Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105444 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 88708 invoked from network); 25 Apr 2019 13:08:20 -0000 Received: from unknown (HELO mail-vs1-f68.google.com) (209.85.217.68) by pb1.pair.com with SMTP; 25 Apr 2019 13:08:20 -0000 Received: by mail-vs1-f68.google.com with SMTP id g127so12154719vsd.6 for ; Thu, 25 Apr 2019 03:09:12 -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=o1H/hYwRffshO6kdEjY9orwfItVqCHbPoQtXWHk44JU=; b=Vhy2pr3ym59wTshuNLUj6sZPuHDiiBsPNVUhx+e4BBuiUr1uWRZGuneAPt/mZtfI3Q 0z5ZXP8CbGwKUZFbvI2aLkHw5LadTMr6vmqCCdj66CV8w7MFuNOGBOaaZDvad2L2AvS3 /KDZ+4TWWqIJRGKzA4NHVIT5/5gCH2SD031Xjp+Aa+Vm4VbUyu2hFNGhuxb8aMicx9kW ViKxgrLTp/root0/saSNDv+IST1ZNAT2VqwRQpsf6ioAK45DoAlBF1d40Dp3/fkYfLVN SzZj3m9eBtQYlwYMk/zJD1lbV6LDvUqXIvOuJMKbK7UYHNAAxyZ+i6CoH+gF297A+T/m v2og== X-Gm-Message-State: APjAAAWn6IVbGUn4+unVmZpaqb4Mu6pwxI8MWez6QJbYfBDvyBRhrEZD RrvIbZ7bmQfvVSKDhZBLV540n8nIdyN4bKBsOpE= X-Google-Smtp-Source: APXvYqyWN7rBrCUgzS5LDrfxQ8nBLjAHdHwT4UczkwiOl3YP+QT09K6Egq20f2FYTt7nwuBNeRd+Xs7T24zs+/oYlwo= X-Received: by 2002:a67:f3c9:: with SMTP id j9mr17707742vsn.21.1556186952173; Thu, 25 Apr 2019 03:09:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: bishop@php.net Date: Thu, 25 Apr 2019 06:08:45 -0400 Message-ID: To: Nikita Popov Cc: Bob Weinand , PHP internals Content-Type: multipart/alternative; boundary="0000000000007d0e22058758022d" Subject: Re: [PHP-DEV] [RFC] Change the precedence of the concatenation operator From: bishop@php.net (Bishop Bettini) --0000000000007d0e22058758022d Content-Type: text/plain; charset="UTF-8" On Thu, Apr 25, 2019 at 5:52 AM Nikita Popov wrote: > On Thu, Mar 28, 2019 at 2:33 PM Bob Weinand wrote: > > > I feel like concatenation having the same precedence than addition and > > subtraction is promoting programmers to make mistakes. Albeit typically > > easy to catch ones, it is a quality of life change at least. > > > > Hence I'm proposing a RFC changing the precedences: > > https://wiki.php.net/rfc/concatenation_precedence > > Similarly to the ternary associativity RFC, I've analyzed the top 2000 > composer packages and checked whether they would be affected by this > change: https://gist.github.com/nikic/a4df3e8e18c7955c2c21cf6cdb4cbfaa > > The tl;dr is that there were 5 instances where behavior would change per > this RFC, and all 5 of them are bugs in current code and would be > interpreted correctly after this RFC. > 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."), so I'd encourage bringing this to a vote. I'm a +1. --0000000000007d0e22058758022d--