[#33640] [Ruby 1.9-Bug#4136][Open] Enumerable#reject should not inherit the receiver's instance variables — Hiro Asari <redmine@...>

Bug #4136: Enumerable#reject should not inherit the receiver's instance variables

10 messages 2010/12/08

[#33667] [Ruby 1.9-Bug#4149][Open] Documentation submission: syslog standard library — mathew murphy <redmine@...>

Bug #4149: Documentation submission: syslog standard library

11 messages 2010/12/10

[#33683] [feature:trunk] Enumerable#categorize — Tanaka Akira <akr@...>

Hi.

14 messages 2010/12/12
[#33684] Re: [feature:trunk] Enumerable#categorize — "Martin J. Dst" <duerst@...> 2010/12/12

[#33687] Towards a standardized AST for Ruby code — Magnus Holm <judofyr@...>

Hey folks,

23 messages 2010/12/12
[#33688] Re: Towards a standardized AST for Ruby code — Charles Oliver Nutter <headius@...> 2010/12/12

On Sun, Dec 12, 2010 at 9:55 AM, Magnus Holm <judofyr@gmail.com> wrote:

[#33689] Re: Towards a standardized AST for Ruby code — "Haase, Konstantin" <Konstantin.Haase@...> 2010/12/12

On Dec 12, 2010, at 17:46 , Charles Oliver Nutter wrote:

[#33763] [Ruby 1.9-Bug#4168][Open] WeakRef is unsafe to use in Ruby 1.9 — Brian Durand <redmine@...>

Bug #4168: WeakRef is unsafe to use in Ruby 1.9

43 messages 2010/12/17

[#33815] trunk warnflags build issue with curb 0.7.9? — Jon <jon.forums@...>

As this may turn out to be a 3rd party issue rather than a bug, I'd like some feedback.

11 messages 2010/12/22

[#33833] Ruby 1.9.2 is going to be released — "Yuki Sonoda (Yugui)" <yugui@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2010/12/23

[#33846] [Ruby 1.9-Feature#4197][Open] Improvement of the benchmark library — Benoit Daloze <redmine@...>

Feature #4197: Improvement of the benchmark library

15 messages 2010/12/23

[#33910] [Ruby 1.9-Feature#4211][Open] Converting the Ruby and C API documentation to YARD syntax — Loren Segal <redmine@...>

Feature #4211: Converting the Ruby and C API documentation to YARD syntax

10 messages 2010/12/26

[#33923] [Ruby 1.9-Bug#4214][Open] Fiddle::WINDOWS == false on Windows — Jon Forums <redmine@...>

Bug #4214: Fiddle::WINDOWS == false on Windows

15 messages 2010/12/27

[ruby-core:33774] [Ruby 1.9-Feature#4172][Open] Named arguments/parameters support

From: Rodrigo Rosenfeld Rosas <redmine@...>
Date: 2010-12-19 23:13:36 UTC
List: ruby-core #33774
Feature #4172: Named arguments/parameters support
http://redmine.ruby-lang.org/issues/show/4172

Author: Rodrigo Rosenfeld Rosas
Status: Open, Priority: Low
Assigned to: Yukihiro Matsumoto, Category: core, Target version: 2.0

It is usual in the Ruby community to use the idiom

def method(options={})
  param1, param2 = options.values_at(:param1, :param2) # or {param1: 'default1', param2: 2}.collect{|k, v| options[k] || v }
  ...
end

instead of

def method(param1, param2)
  ...
end

Perl 6 supports named arguments (or parameters) out-of-the-box. Suppose the following method (not valid Ruby actually):

def tag(tag_name, :content(''), :attributes({}), :closing_tag(true))
  ...
end

It would be great if this could be called as

hr = tag('hr', closing_tag -> false, attributes -> {style: 'color: blue'})

It think it should be even possible to call it like

tag(tag_name: 'div', content: 'Ruby is getting even more awesome with this feature!')

I think it is much more legible than 

tag('hr', '', {}, false)

or than using an 'options' hash parameter.

Is there any reasons why Ruby doesn't support named parameters as part of the syntax?


----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next