[#87467] [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError — mofezilla@...
Issue #14841 has been reported by hirura (Hiroyuki URANISHI).
3 messages
2018/06/10
[#87515] [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError — hirura@...
Issue #14841 has been updated by hirura (Hiroyuki URANISHI).
7 messages
2018/06/19
[#87516] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
hirura@gmail.com wrote:
[#87517] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
Sorry, I left this out: If you can reproduce it again, can you
[#87519] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— hirura <hirura@...>
2018/06/19
Hi Eric,
[#87521] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
hirura <hirura@gmail.com> wrote:
[#87541] [Ruby trunk Feature#14859] [PATCH] implement Timeout in VM — normalperson@...
Issue #14859 has been reported by normalperson (Eric Wong).
4 messages
2018/06/21
[#87605] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been reported by k0kubun (Takashi Kokubun).
3 messages
2018/06/23
[#87614] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — normalperson@...
Issue #14867 has been updated by normalperson (Eric Wong).
4 messages
2018/06/23
[#87631] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been updated by k0kubun (Takashi Kokubun).
5 messages
2018/06/25
[#87635] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process
— Eric Wong <normalperson@...>
2018/06/25
takashikkbn@gmail.com wrote:
[#87665] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — eregontp@...
Issue #14867 has been updated by Eregon (Benoit Daloze).
4 messages
2018/06/28
[#87710] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — Greg.mpls@...
Issue #14867 has been updated by MSP-Greg (Greg L).
3 messages
2018/06/30
[ruby-core:87412] [Ruby trunk Bug#14824] Endless Range Support in irb
From:
mame@...
Date:
2018-06-05 07:32:08 UTC
List:
ruby-core #87412
Issue #14824 has been updated by mame (Yusuke Endoh). First of all, I have no strong opinion about this issue. The current behavior of irb looks weird to me, but it may be okay because irb users can work around the issue easily. In principle, I expect irb to cut the shortest lines that parses. For example, consider the following input: ``` foo .bar ``` Irb first evaluates only the first line `foo`, and the second line `.bar` causes SyntaxError. This is the behavior that I expect. In the same logic, I expect `1..` to be cut because it parses. ``` irb(main):001:0> 1.. ``` BTW, a line `obj.+` causes line continuation. This is a behavior that I don't expect: ``` irb(main):001:0> obj = Object.new => #<Object:0x0000560275fa4b00> irb(main):002:0> def obj.+(); 42; end => :+ irb(main):003:0> obj.+ irb(main):004:0* irb(main):005:0* ; => 42 ``` If the method name is different than `+`, say `foo`, irb does not wait for the next line. Looks very inconsistent. ``` irb(main):006:0> def obj.foo(); 42;end => :foo irb(main):007:0> obj.foo => 42 ``` So, I cannot see any consistent policy about line continuation. But again, it's okay to me in the case of irb. Few users will encounter such a corner case. Even if someone does, s/he can avoid such a behavior by explicit semicolon or parens or something else. ---------------------------------------- Bug #14824: Endless Range Support in irb https://bugs.ruby-lang.org/issues/14824#change-72399 * Author: jeremyevans0 (Jeremy Evans) * Status: Rejected * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0preview2 (2018-05-31 trunk 63539) [x86_64-openbsd] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- `irb` currently doesn't have great support for endless ranges, forcing you to use explicit parentheses around the endless range. Without explicit parentheses, it treats the endless range as a line continuation. ~~~ irb(main):001:0> 1.. irb(main):002:0* ; => 1.. irb(main):003:0> (1..) => 1.. irb(main):004:0> ~~~ Ranges with ends do not require parentheses in `irb`, and endless ranges should have the same behavior. -- 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>