Ian MacLeod

  • Email:
  • Registered on: 07/01/2011
  • Last connection: 02/23/2013

Activity

Reported issues: 3

02/23/2013

11:22 AM ruby-trunk Bug #921: autoload is not thread-safe
Apologies in advance if this is the wrong place to get clarification:
It's been widely circulated that autoload is d...

01/07/2013

10:25 AM ruby-trunk Feature #7657: Array#& doesn't accept Enumerables
Let me see if I understand the implicit conversion cases:
* If an object implements #to_ary, #to_str, etc - it is as...

01/06/2013

09:02 AM ruby-trunk Feature #7657: Array#& doesn't accept Enumerables
Err, I mean it looks like it's similar to http://bugs.ruby-lang.org/issues/1028
09:00 AM ruby-trunk Feature #7657 (Open): Array#& doesn't accept Enumerables
This seems similar to http://bugs.ruby-lang.org/issues/6923
Example:
irb(main):001:0> class Thing
irb(...

12/28/2012

05:57 AM ruby-trunk Bug #7626: Bizarre Array#fetch behavior with a block when index is out of bounds
Oh! It's a block form of `default` - I get it now. Disregard!
05:53 AM ruby-trunk Bug #7626: Bizarre Array#fetch behavior with a block when index is out of bounds
Why would you need to call fetch with a block if you already know the index is out of range? You already have the in...
03:46 AM ruby-trunk Bug #7626 (Rejected): Bizarre Array#fetch behavior with a block when index is out of bounds
This also occurs on Ruby 1.8.
First, the example, taken almost directly from the docs (except the docs only descri...

04/28/2012

01:07 AM ruby-trunk Bug #4044: Regex matching errors when using \W character class and /i option
One additional note is that this only seems to occur when \W is in a character group:
➜ ruby -ve '("a".."z").each {...

07/01/2011

06:27 AM Backport92 Backport #4952: Integer#chr(Encoding::*) behaves inconsistently with negative or large values
This appears to be related to and likely a duplicate of http://redmine.ruby-lang.org/issues/4869
06:15 AM Backport92 Backport #4952 (Open): Integer#chr(Encoding::*) behaves inconsistently with negative or large values
These seem like they should all be raising RangeError; and appear to indicate that values are overflowing/being cast ...

Also available in: Atom