[#85940] [Ruby trunk Bug#14578] Forking a child process inside of a mutex crashes the ruby interpreter — ben.govero@...
Issue #14578 has been reported by bengovero (Ben Govero).
3 messages
2018/03/05
[#86205] [Ruby trunk Feature#14618] Add display width method to String for CLI — aycabta@...
Issue #14618 has been reported by aycabta (aycabta .).
3 messages
2018/03/19
[#86366] Re: [ruby-cvs:70102] usa:r63008 (trunk): get rid of test error/failure on Windows introduced at r62955 — Eric Wong <normalperson@...>
usa@ruby-lang.org wrote:
3 messages
2018/03/28
[ruby-core:85872] [Ruby trunk Bug#14562] Do not warn for assignment in conditionals inside ()
From:
ronnie@...
Date:
2018-03-01 01:15:55 UTC
List:
ruby-core #85872
Issue #14562 has been reported by matsuda (Akira Matsuda). ---------------------------------------- Bug #14562: Do not warn for assignment in conditionals inside () https://bugs.ruby-lang.org/issues/14562 * Author: matsuda (Akira Matsuda) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-03-01 trunk 62617) [x86_64-darwin16] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- Ruby warns against this code, which is very helpful. ``` % ruby -we 'if a=1; p a; end' -e:1: warning: found = in conditional, should be == 1 ``` So there's a commonly known practice. In order to express that we're intentionally assigning (not missing one more = sign), we usually add parens around the assignment. But in fact, Ruby still warns... ``` % ruby -we 'if (a=1); p a; end' -e:1: warning: found = in conditional, should be == 1 ``` Can this behavior changed not to warn when parenthesized? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>