From: matz@... Date: 2020-01-16T06:18:53+00:00 Subject: [ruby-core:96890] [Ruby master Bug#10388] Operator precedence problem in multiple assignment (massign) Issue #10388 has been updated by matz (Yukihiro Matsumoto). We are not going to change the behavior. We may warn (with `-W`) if we see the simple assignments on the right-hand side of multiple assignments. Matz. ---------------------------------------- Bug #10388: Operator precedence problem in multiple assignment (massign) https://bugs.ruby-lang.org/issues/10388#change-83902 * Author: knu (Akinori MUSHA) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: * ruby -v: ruby 2.2.0dev (2014-10-13 trunk 47904) [x86_64-freebsd10] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- I understand it wouldn't be easy to fix this, but since I happened to find it here it goes. - `a, b = c = 1, 2` is currently taken as `a, b = (c = 1), 2`; I'd expect it to be taken as `a, b = (c = 1, 2)`. - `a, b = *c = 1, 2` is currently taken as `a, b = *(c = 1), 2`; I'd expect it to be taken as `a, b = *(c = 1, 2)` or even `a, b = (*c = 1, 2)`. - `a, b = c, d = 1, 2` is currently taken as `a, b = (c), (d = 1), 2`; I'd expect it to be taken as `a, b = (c, d = 1, 2)`. Should they be fixed/changed or not, issuing a warning would be greatly helpful. -- https://bugs.ruby-lang.org/ Unsubscribe: