Ruby Issue Tracking System

02/02/2014

03:01 AM Ruby Feature #8987: map/collect extension which handles arguments

Tsuyoshi Sawada wrote:
> Probably, it makes more sense to extend the syntax of `Symbol#to_proc`. The conventional `Symbol#to_proc` does not take an argument:
+1
henry.maddocks (Henry Maddocks)

11/13/2013

08:04 AM Ruby Feature #8257: Exception#cause to carry originating exception along with new one

How is this different to 'wrapping' an exception? Eg.
http://www.jayway.com/2011/05/25/ruby-an-exceptional-language/
henry.maddocks (Henry Maddocks)

05/09/2013

05:54 PM Ruby Feature #8377: Deprecate :: for method calls in 2.1

rubiii (Daniel Harrington) wrote:
> I'm also very much in favour of this change for simplicity.
> ...
But '.' and '::' mean different things.
'::' means you are calling the method that is defined inside the Nokogiri module/namespace... henry.maddocks (Henry Maddocks)

05:35 PM Ruby Feature #8377: Deprecate :: for method calls in 2.1

phluid61 (Matthew Kerwin) wrote:
> =begin
> ...
C++ and PHP also use the scope resolution operator.
As for the rest of what you said, I don't understand.
henry.maddocks (Henry Maddocks)

05/08/2013

08:56 AM Ruby Feature #8377: Deprecate :: for method calls in 2.1

charliesome (Charlie Somerville) wrote:
> (({::})) is usually a constant lookup operator, but it can also be used to call methods.
Is it? I thought it was the scope resolution operator.
charliesome (Charlie Somerville) wrote:
> ... henry.maddocks (Henry Maddocks)

04/27/2013

12:27 PM Ruby Feature #8237: Logical method chaining via inferred receiver

wardrop (Tom Wardrop) wrote:
> =begin
> ...
Object#tap wasn't introduced to avoid unnecessary temporary variable assignments. #tap is an implementation of the K combinator which has lots of uses beyond avoiding unnecessary temporaries.... henry.maddocks (Henry Maddocks)

04/23/2013

04:54 PM Ruby Bug #8309: Editorializing in rexml::ie_hack documentation

Don't hold back...
http://www.mikeperham.com/2010/12/08/contributing-to-ruby/
henry.maddocks (Henry Maddocks)

04/15/2013

12:02 PM Ruby Feature #8237: Logical method chaining via inferred receiver

wardrop (Tom Wardrop) wrote:
> =begin
> ...
If you want your request to be taken seriously your example usage should show that you have thoroughly considered how this feature will be used, how it will effect existing code, and the edge... henry.maddocks (Henry Maddocks)

04/09/2013

02:29 PM Ruby Feature #8237: Logical method chaining via inferred receiver

I don't support this because inferred or implicit variables are a 'Perlism' that we should avoid. It makes programs difficult to understand and it is easy to add subtle bugs that are hard to track down.
The sample usages are poor co... henry.maddocks (Henry Maddocks)

05/20/2012

01:54 PM Ruby Feature #6470: Make attr_accessor return the list of generated method

Aren't accessors public by definition? If you want them to be private use attr.
henry.maddocks (Henry Maddocks)