[#90865] [Ruby trunk Bug#15499] Breaking behavior on ruby 2.6: rb_thread_call_without_gvl doesn't invoke unblock_function when used on the main thread — apolcyn@...
Issue #15499 has been reported by apolcyn (alex polcyn).
3 messages
2019/01/03
[#90877] [Ruby trunk Bug#15499] Breaking behavior on ruby 2.6: rb_thread_call_without_gvl doesn't invoke unblock_function when used on the main thread — apolcyn@...
Issue #15499 has been updated by apolcyn (alex polcyn).
3 messages
2019/01/03
[#90895] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707)) — Eric Wong <normalperson@...>
ko1c-failure@atdot.net wrote:
4 messages
2019/01/05
[#90896] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707))
— Takashi Kokubun <takashikkbn@...>
2019/01/05
Thanks to explain that.
[#91200] [Ruby trunk Feature#15553] Addrinfo.getaddrinfo supports timeout — glass.saga@...
Issue #15553 has been reported by Glass_saga (Masaki Matsushita).
4 messages
2019/01/21
[#91289] Re: [Ruby trunk Feature#15553] Addrinfo.getaddrinfo supports timeout
— Eric Wong <normalperson@...>
2019/01/26
glass.saga@gmail.com wrote:
[ruby-core:91242] [Ruby trunk Bug#15537] Numeric#step doesn't iterate under some conditions
From:
muraken@...
Date:
2019-01-24 02:22:43 UTC
List:
ruby-core #91242
Issue #15537 has been updated by mrkn (Kenta Murata).
Assignee set to mrkn (Kenta Murata)
Status changed from Open to Assigned
----------------------------------------
Bug #15537: Numeric#step doesn't iterate under some conditions
https://bugs.ruby-lang.org/issues/15537#change-76487
* Author: shuujii (Shuji KOBAYASHI)
* Status: Assigned
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* Target version:
* ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Numeric#step doesn't iterate under the following conditions:
- receiver and/or `by` are `Float`
- `by` is negative
- `to` is default
- without block
### Example:
Good:
~~~ruby
p 1.step(by: 3).take(2) #=> [1, 4]
p 1.step(by: -3).take(2) #=> [1, -2]
p 1.step(by: 3.0).take(2) #=> [1.0, 4.0]
p 1.0.step(by: 3).take(2) #=> [1.0, 4.0]
a=[]; p 1.step(by: -3.0){|n|break a if (a << n).size == 2} #=> [1.0, -2.0]
a=[]; p 1.0.step(by: -3){|n|break a if (a << n).size == 2} #=> [1.0, -2.0]
~~~
Bad:
~~~ruby
p 1.step(by: -3.0).take(2) #=> []
p 1.0.step(by: -3).take(2) #=> []
~~~
I have attached a patch.
---Files--------------------------------
fix-numeric-step-for-float.patch (2.07 KB)
--
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>