[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
[email protected] wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <[email protected]> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/12/30
[ruby-core:90694] [Ruby trunk Bug#15457][Closed] Weird behaviour when having multiple arguments of same name and splat operator
From:
mame@...
Date:
2018-12-24 09:08:34 UTC
List:
ruby-core #90694
Issue #15457 has been updated by mame (Yusuke Endoh).
Status changed from Open to Closed
Thank you. This is duplicate of #14611. The behavior has been changed in trunk (and 2.6).
```
$ cat bug.rb
def test(_a, b, *_a)
pp _a
pp b
end
test(*%W{a b c d e})
$ ./local/bin/ruby -v bug.rb
ruby 2.6.0dev (2018-12-24 trunk 66525) [x86_64-linux]
"a"
"b"
```
#14611 is marked as backport required. Please wait.
----------------------------------------
Bug #15457: Weird behaviour when having multiple arguments of same name and splat operator
https://bugs.ruby-lang.org/issues/15457#change-75869
* Author: graywolf (Gray Wolf)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.5.3
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
When multiple arguments of the same name are provided and last one of
them has splat operator, everything gets weird.
```
+ $ cat bug.rb
def test(_a, b, *_a)
pp _a
pp b
end
test(*%W{a b c d e})
+ $ RUBYOPT=-rpry rvm 2.5.3 do ruby bug.rb
["c", "d", "e"]
nil
+ $ RUBYOPT=-rpry rvm 2.4.5 do ruby bug.rb
["c", "d", "e"]
nil
+ $ RUBYOPT=-rpry rvm 2.3.8 do ruby bug.rb
["c", "d", "e"]
nil
```
At least it's consistent across supported ruby versions, but I have no
idea what is going on.
I get why `_a` is `%w{c d e}`, that makes sense. But why is `b` `nil`?
That makes no sense at all.
It looks to me like an edge case when having multiple arguments of the same
name and one of them (last one?) having splat operator.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>