Ruby Issue Tracking System

11/04/2016

04:54 PM Ruby trunk Feature #12901 (Open): Anonymous functions without scope lookup overhead

Right now if you are writing performance sensitive code you can get a performance bump by not using anonymous functio...

07/07/2016

07:59 PM Ruby trunk Feature #12217: Introducing Enumerable#sum for precision compensated summation and revert r54237

Would be nice if we could match behavior with Rails Enumerable#sum https://github.com/rails/rails/blob/3d716b9e66e334...

06/20/2016

01:45 PM Ruby trunk Feature #11955: Expose Object that Receives logs in Logger

Sorry for the delay, bugs.ruby-lang.org does not send me emails for some reason.
The first patch I attached return...

04/21/2016

03:29 PM Ruby trunk Feature #12306: Implement String #blank? #present? and improve #strip and family to handle unicode

I think this is useful outside of Rails. The Active Support module has 87 million downloads on rubygems.org while Rai...

03/15/2016

04:42 PM Ruby trunk Feature #11955: Expose Object that Receives logs in Logger

Anything else that needs to be done for this patch?

01/21/2016

04:04 PM Ruby trunk Misc #12004: Code of Conduct

I'm in favor of the contributor covenant, a version of it was adopted by Rails. So far it has not produced any of the...

01/19/2016

08:03 PM Ruby trunk Feature #11955: Expose Object that Receives logs in Logger

Nobu, I've added a new patch that would expose the `LogDevice` object in a `Logger` instance. This would be acceptabl...

01/08/2016

05:00 PM Ruby trunk Feature #11955: Expose Object that Receives logs in Logger

> Your example doesn't seem to able to get rid of adding stdout_logger twice or more, even with logger.destination.
...

01/06/2016

04:27 PM Ruby trunk Feature #11955: Expose Object that Receives logs in Logger

Here is a patch to Rails that could benefit from standardizing access to the logger destination object: https://githu...

01/05/2016

09:59 PM Ruby trunk Feature #11955 (Assigned): Expose Object that Receives logs in Logger

I need to be able to perform logic based on the destination of a current logger, this is currently not possible witho...