[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>
Issue #18465 has been reported by ioquatix (Samuel Williams).
16 messages
2022/01/09
[#107150] [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically — "ko1 (Koichi Sasada)" <noreply@...>
Issue #18494 has been updated by ko1 (Koichi Sasada).
4 messages
2022/01/17
[#107170] Re: [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically
— Eric Wong <normalperson@...>
2022/01/17
> https://bugs.ruby-lang.org/issues/18494
[#107302] [Ruby master Bug#18553] Memory leak on compiling method call with kwargs — "ibylich (Ilya Bylich)" <noreply@...>
Issue #18553 has been reported by ibylich (Ilya Bylich).
4 messages
2022/01/27
[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>
Issue #18557 has been reported by mame (Yusuke Endoh).
18 messages
2022/01/29
[ruby-core:107104] [Ruby master Bug#18486] Enumerable#group_by ordering appears to have changed and doesn't match docs.
From:
"matsuda (Akira Matsuda)" <noreply@...>
Date:
2022-01-13 19:12:43 UTC
List:
ruby-core #107104
Issue #18486 has been updated by matsuda (Akira Matsuda).
> group_by emerged in Ruby 1.8.7, but my RVM can't install it :(
> The earliest I could check was 1.9.3, and it already has order of keys 1, 2, 0.
off-topic: all-ruby is your friend :) https://github.com/akr/all-ruby
```
$ docker run -it --rm rubylang/all-ruby ./all-ruby -e 'p (1..6).to_a.inject({}) { |r, i| (r[i % 3] ||= []) << i; r }'
ruby-0.49 -e:1: syntax error
(snip)
ruby-1.6.8 1..6
-e:1: undefined method `inject' for []:Array (NameError)
exit 1
ruby-1.8.0 {0=>[3, 6], 1=>[1, 4], 2=>[2, 5]}
...
ruby-1.8.7-p374 {0=>[3, 6], 1=>[1, 4], 2=>[2, 5]}
ruby-1.9.0-0 {1=>[1, 4], 2=>[2, 5], 0=>[3, 6]}
...
ruby-3.1.0 {1=>[1, 4], 2=>[2, 5], 0=>[3, 6]}
```
----------------------------------------
Bug #18486: Enumerable#group_by ordering appears to have changed and doesn't match docs.
https://bugs.ruby-lang.org/issues/18486#change-95950
* Author: [email protected] (kay rhodes)
* Status: Closed
* Priority: Normal
* ruby -v: 3.0.2
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
The documentation for Enumerable#group_by suggests the following:
(1..6).group_by { |i| i%3 } #=> {0=>[3, 6], 1=>[1, 4], 2=>[2, 5]}
it actually produces this (same values different order). Tested in 2.6.3 and 3.0.2
(1..6).group_by { |i| i%3 } #=> {1=>[1, 4], 2=>[2, 5], 0=>[3, 6]}
as hash table ordering is something people depend on these days I wonder if the reordering of the keys may be more than just a minor documentation bug.
I noticed this in 2.6.3. Assuming the docs matched reality when written this implies we've been living with this for a while. I don't know how long before that this actually changed.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>