Shugo Maeda

  • Registered on: 05/08/2008
  • Last connection: 03/20/2015

Projects

Activity

Reported issues: 52

08/29/2015

02:22 PM Ruby trunk Feature #11476 (Assigned): Methods defined in Refinements cannot be called via send
It's an intended behavior that Kernel#send ignores refinements as described at https://bugs.ruby-lang.org/projects/ru...

08/07/2015

03:46 PM Ruby trunk Bug #11407 (Third Party's Issue): Net::FTP nlst method return wrong data and don't raise Error wh...

08/02/2015

12:29 PM Ruby trunk Bug #11407: Net::FTP nlst method return wrong data and don't raise Error when path is wrong
Damian Giebas wrote:
> When ftp server is on Linux all is fine. Problem is when FTP is on IIS Server 8.0 (and probab...

07/30/2015

02:33 PM Ruby trunk Bug #11407 (Feedback): Net::FTP nlst method return wrong data and don't raise Error when path is ...
Damian Giebas wrote:
> I found bug in nlst function. When we have situatiuon on ftp like this
>
> /
> my_folde...

06/29/2015

05:52 AM Ruby trunk Revision 51060: * eval.c (add_activated_refinement): should not include the original
class.

06/27/2015

09:04 AM Ruby trunk Bug #11260 (Assigned): [PATCH] Net::FTP keeps a TCPServer opened when sending the data port fails
Benoit Daloze wrote:
> @shugo, can I commit this?
The patch looks fine. Please commit it.

06/24/2015

06:07 AM Ruby trunk Bug #11247 (Assigned): Should position of `using` affect the behavior?
Koichi Sasada wrote:
> Recent fix changed behavior of this script.
>
> * trunk in May: C and R1, C
> * current t...
06:02 AM Ruby trunk Bug #11246 (Rejected): refine block doesn't respect "lexical" refinement information
Koichi Sasada wrote:
> The following program making two refinements refine class C.
>
> ```ruby
> class C
> d...

05/29/2015

02:06 AM Ruby trunk Bug #11182: Refinement with alias causes strange behavior
Koichi Sasada wrote:
> Wait. `each` is not good terminology for our project. Use `iterate` intead.
>
> ```ruby
>...

05/28/2015

08:03 AM Ruby trunk Bug #11182 (Feedback): Refinement with alias causes strange behavior
Koichi Sasada wrote:
> With model (1), it seems C#foo will be called.
> WIth model (2), it seems M::C#foo will be c...

Also available in: Atom