General

Profile

Shugo Maeda

  • Registered on: 05/08/2008
  • Last connection: 05/13/2016

Issues

Projects

Activity

05/13/2016

09:04 AM Ruby trunk Feature #12375: Net::HTTP.post
Usaku NAKAMURA wrote:
> Shugo Maeda wrote:
> > * The first argument must be a URI object, but it might be better to...
07:56 AM Ruby trunk Feature #12375 (Open): Net::HTTP.post
Net::HTTP.post_form is convenient, but it's dedicated to application/x-www-form-urlencoded.
Why not provide Net::HTT...

03/04/2016

08:48 AM Ruby trunk Feature #11547: remove top-level constant lookup
Scott Bronson wrote:
> Corin, I completely agree. Recently, Rails's nondeterministic autoload made it very hard for...

02/19/2016

07:34 AM Ruby trunk Feature #12086 (Open): using: option for instance_eval etc.
Currently refinements can be activated only in toplevel or class/module definitions.
If they can be activated in blo...

01/23/2016

11:57 AM Ruby trunk Bug #12007 (Open): Newly added Unicode data file doesn't get downloaded
It seems that RubyCI was broken by this change.
from http://rubyci.s3.amazonaws.com/tk2-243-31075/ruby-trunk/log/2...
11:24 AM Ruby trunk Bug #12003: Unexpected behavior of === with Range of Date objects
Ross Kaffenberger wrote:
> In Ruby 2.2, a Range of Date objects will return true when matched with === for a new Dat...
11:15 AM Ruby trunk Bug #12003 (Closed): Unexpected behavior of === with Range of Date objects
Applied in changeset r53635.
----------
* range.c (range_eqq): revert r11113 because rb_call_super() is
called in ...

01/22/2016

02:41 AM Ruby trunk Misc #12004: Code of Conduct
Yukihiro Matsumoto wrote:
> The project maintainers here mean a subset of contributors who have privilege to modify ...

01/20/2016

03:34 PM Ruby trunk Misc #12004: Code of Conduct
Yukihiro Matsumoto wrote:
> I agree with the spirit of anti harassment. I hope the community being free from any per...

01/08/2016

01:48 AM Ruby trunk Bug #11954 (Assigned): "self has wrong type to call super in this context" under weird circumstances
The bug was introduced in r52104 by ko1, and it seems to be fixed by the attached patch, but Im' not sure.

Also available in: Atom