[#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:91088] [Ruby trunk Bug#15535] Optional arguments for definition - SyntaxError is not the correct Error type
From:
waheed.barghouthi@...
Date:
2019-01-14 19:52:05 UTC
List:
ruby-core #91088
Issue #15535 has been reported by waheedi (Waheed Barghouthi). ---------------------------------------- Bug #15535: Optional arguments for definition - Syntax Error is not the correct Error type https://bugs.ruby-lang.org/issues/15535 * Author: waheedi (Waheed Barghouthi) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: 2.6.0p0 * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- The below definition throws a syntax Error, while it there is no syntax error and I'm not sure what is the intention behind the Syntax error `def hello(foo="bar", bar, yanko="me")` `p "Hello"` `end` The same definition below with a tiny modification in the argument set, give a Syntax OK. `def hello(foo="bar", bar="foo", yanko="me")` `p "Hello"` `end` It seems when there is a required argument in the definition that happens to be in between optional arguments that is a Syntax Error, I think another Error should be triggered if that intended to be made by design to error! This has been tested on mostly every ruby version after 1.8.7 and its gave the same result. -- 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>