[#53944] [ruby-trunk - Bug #8210][Open] Multibyte character interfering with end-line character within a regex — "sawa (Tsuyoshi Sawada)" <sawadatsuyoshi@...>

14 messages 2013/04/03

[#53974] [ruby-trunk - Feature #8215][Open] Support accessing Fiber-locals and backtraces for a Fiber — "halorgium (Tim Carey-Smith)" <ruby-lang-bugs@...>

14 messages 2013/04/03

[#54095] [ruby-trunk - Feature #8237][Open] Logical method chaining via inferred receiver — "wardrop (Tom Wardrop)" <tom@...>

34 messages 2013/04/08

[#54138] [ruby-trunk - Bug #8241][Open] If uri host-part has underscore ( '_' ), 'URI#parse' raise 'URI::InvalidURIError' — "neocoin (Sangmin Ryu)" <neocoin@...>

9 messages 2013/04/09

[#54185] [CommonRuby - Feature #8257][Open] Exception#cause to carry originating exception along with new one — "headius (Charles Nutter)" <headius@...>

43 messages 2013/04/11

[#54196] Encouraging use of CommonRuby — Charles Oliver Nutter <headius@...>

I think we need to do more to encourage the use of the CommonRuby

20 messages 2013/04/11
[#54200] Re: Encouraging use of CommonRuby — Marc-Andre Lafortune <ruby-core-mailing-list@...> 2013/04/11

Hi,

[#54211] Re: Encouraging use of CommonRuby — "NARUSE, Yui" <naruse@...> 2013/04/12

As far as I understand, what is CommonRuby and the process over CommonRuby

[#54215] Re: Encouraging use of CommonRuby — Charles Oliver Nutter <headius@...> 2013/04/12

On Thu, Apr 11, 2013 at 11:25 PM, NARUSE, Yui <naruse@airemix.jp> wrote:

[#54207] [CommonRuby - Feature #8258][Open] Dir#escape_glob — "steveklabnik (Steve Klabnik)" <steve@...>

15 messages 2013/04/12

[#54218] [CommonRuby - Feature #8259][Open] Atomic attributes accessors — "funny_falcon (Yura Sokolov)" <funny.falcon@...>

43 messages 2013/04/12

[#54288] [CommonRuby - Feature #8271][Open] Proposal for moving to a more visible, formal process for feature requests — "headius (Charles Nutter)" <headius@...>

15 messages 2013/04/15

[#54333] Requesting Commit Access — Aman Gupta <ruby@...1.net>

Hello ruby-core,

16 messages 2013/04/16

[#54473] [Backport 200 - Backport #8299][Open] Minor error in float parsing — "bobjalex (Bob Alexander)" <bobjalex@...>

27 messages 2013/04/19

[#54532] [ruby-trunk - Bug #8315][Open] mkmf does not include include paths from pkg_config anymore — "Hanmac (Hans Mackowiak)" <hanmac@...>

11 messages 2013/04/23

[#54621] [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI — "ko1 (Koichi Sasada)" <redmine@...>

43 messages 2013/04/27
[#54643] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI — "authorNari (Narihiro Nakamura)" <authorNari@...> 2013/04/28

[#54649] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI — SASADA Koichi <ko1@...> 2013/04/28

(2013/04/28 9:23), authorNari (Narihiro Nakamura) wrote:

[#54657] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI — Magnus Holm <judofyr@...> 2013/04/28

On Sat, Apr 27, 2013 at 8:19 PM, ko1 (Koichi Sasada)

[#54665] [ruby-trunk - Bug #8344][Open] Status of Psych and Syck — "Eregon (Benoit Daloze)" <redmine@...>

18 messages 2013/04/28

[ruby-core:54596] Re: [ruby-trunk - Bug #8040] Unexpect behavior when using keyword arguments

From: Zachary Scott <zachary@...>
Date: 2013-04-26 06:32:06 UTC
List: ruby-core #54596
Assign to nagachika-san
On Apr 24, 2013 10:53 PM, "marcandre (Marc-Andre Lafortune)" <
ruby-core@marc-andre.ca> wrote:

>
> Issue #8040 has been updated by marcandre (Marc-Andre Lafortune).
>
>
> Any hope of getting this in time for next patchlevel release?
> ----------------------------------------
> Bug #8040: Unexpect behavior when using keyword arguments
> https://bugs.ruby-lang.org/issues/8040#change-38882
>
> Author: pabloh (Pablo Herrero)
> Status: Assigned
> Priority: Normal
> Assignee: mame (Yusuke Endoh)
> Category:
> Target version:
> ruby -v: 2.0.0-p0
> Backport:
>
>
> =begin
> There is an odd behavior when calling methods with the new keyword
> arguments syntax, when you have a method defined with mandatory arguments
> that also takes options, like this:
>
>   def foo value, **keywords
>     puts [value,keywords].inspect
>   end
>
>   foo("somthing") #This works
>   foo("somthing", key: 'value') #This also works
>
>   foo(Hash.new(something: 'else')) #This raises 'ArgumentError: wrong
> number of arguments (0 for 1)'
>
> This feels weird regardless the fact that keyword arguments are a Hash at
> the bottom, since you ARE PASSING an argument.
>
> Other side effect from this, is that when you call the method ((|foo|))
> with a single argument, you can't anticipate how many argument you will be
> actually passing at runtime unless you know beforehand the argument's class.
>
> What's maybe even more concerning is the fact than this happens even when
> you pass an argument which class derives from Hash:
>
>   class MyDirectory < Hash; end
>
>   foo(MyDirectory.new(something: 'else')) #This also raises
> 'ArgumentError: wrong number of arguments (0 for 1)'
>
>
> Besides finding this behavior surprising, I think this could also possibly
> lead to old code been unexpectedly broken when updating old methods that
> takes options to the new syntax.
>
> For example if you have this code:
>
>   def foo_with_options argument, options = {}
>     #Do some stuff with options
>   end
>
>
>   #And at someplace else...
>
>   my_hash_thingy = Hash.new
>   foo_with_options(my_hash_thingy) #Only passing mandatory argument, with
> no options, works fine.
>
>
> When updating to the new syntax:
>
>   def foo_with_options argument, an_option: 'value1', another_option:
> 'value2'
>     #Do some stuff with options
>   end
>
>
>
>   #And at someplace else...
>
>   my_hash_thingy = Hash.new
>   foo_with_options(my_hash_thingy) #Only passing mandatory argument, with
> no options, doesn't work anymore.
> =end
>
>
> --
> http://bugs.ruby-lang.org/
>
>

In This Thread