[#84280] [Ruby trunk Bug#14181] hangs or deadlocks from waitpid, threads, and trapping SIGCHLD — nobu@...
Issue #14181 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/12/15
[#84398] [Ruby trunk Bug#14220] WEBrick changes - failures on MSWIN, MinGW — Greg.mpls@...
Issue #14220 has been reported by MSP-Greg (Greg L).
3 messages
2017/12/22
[#84472] Re: [ruby-dev:50394] [Ruby trunk Bug#14240] warn four special variables: $; $, $/ $\ — Eric Wong <normalperson@...>
Shouldn't English posts be on ruby-core instead of ruby-dev?
3 messages
2017/12/26
[ruby-core:84408] [CommonRuby Feature#14224] Boolean class
From:
gabriel.sobrinho@...
Date:
2017-12-22 19:10:15 UTC
List:
ruby-core #84408
Issue #14224 has been reported by sobrinho (Gabriel Sobrinho). ---------------------------------------- Feature #14224: Boolean class https://bugs.ruby-lang.org/issues/14224 * Author: sobrinho (Gabriel Sobrinho) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- Suggestion: TrueClass and FalseClass inheriting from Boolean (new superclass). This would make true/false checking easier, like: ``` unless value.is_a?(Boolean) raise "Non-boolean value" end ``` Currently we have to check for both classes: ``` unless value.is_a?(FalseClass) or value.is_a?(TrueClass) raise "Non-boolean value" end ``` In high-level APIs this would be beneficial, for example in RSpec: ``` expect(value).to be_a Boolean ``` Currently, we have to check like this: ``` expect([TrueClass, FalseClass]).to include value.class ``` Or another similar workaround. I would like to provide a patch if this is acceptable. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>