Eregon (Benoit Daloze)

  • Registered on: 07/30/2009
  • Last connection: 04/22/2018





11:28 AM CommonRuby Feature #8258: Dir#escape_glob
Looks to me like this can be closed since we have Dir.glob(pattern, base: dir) and Pathname#glob uses it.


10:03 AM Ruby trunk Feature #14344: refine at class level
I am a MRI committer. This is just my opinion, but I'm confident it is shared by other committers as well.
I belie...


11:11 AM Ruby trunk Feature #14669: Regexp does not expose the amount of capture groups.
This information is available for named captures via Regexp#names and Regexp#named_captures, but it doesn't seem avai...


09:27 AM Ruby trunk Feature #14666: nil.any?{} should return false
This could maybe be achieved in user code by adding some kind of Optional/Maybe construct, which could include Enumer...


08:48 PM Ruby trunk Revision 9245e097 (ruby-git): Update to ruby/spec@a585ec3
git-svn-id: svn+ssh:// b2dd03c8-39d4-4d8f-98ff-823fe69b080e
08:48 PM Ruby trunk Revision e389e2c5 (ruby-git): Update to ruby/mspec@8b54bf3
git-svn-id: svn+ssh:// b2dd03c8-39d4-4d8f-98ff-823fe69b080e
07:41 PM Ruby trunk Bug #14495: Enumerator::Lazy#uniq invalid state
Should this be backported?


03:00 PM Ruby trunk Bug #14541: Class variables have broken semantics, let's fix them
@Hanmac: Both problems exist, see the example in the description.
The semantics are confusing, that's why I wish we ...
12:24 PM Ruby trunk Bug #14541: Class variables have broken semantics, let's fix them
matz (Yukihiro Matsumoto) wrote:
> It's possible to make those warning replaced by exceptions. I am strongly positiv...
12:12 PM Ruby trunk Feature #13904: getter for original information of Enumerator
This seems fine but very specific.
I still think exposing an Enumerator's receiver, method name and arguments is bet...

Also available in: Atom