[#80974] [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit — ko1@...
Issue #13517 has been updated by ko1 (Koichi Sasada).
4 messages
2017/05/02
[#81024] Re: [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit
— SASADA Koichi <ko1@...>
2017/05/07
sorry for late response.
[#80996] [Ruby trunk Feature#13544] Allow loading an ISeqs sequence directly from a C extension without requiring buffer is in an RVALUE — sam.saffron@...
Issue #13544 has been reported by sam.saffron (Sam Saffron).
3 messages
2017/05/04
[#81016] [Ruby trunk Bug#13526] Segmentation fault at 0x0055c2e58e8920 ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] — s.wanabe@...
Issue #13526 has been updated by wanabe (_ wanabe).
3 messages
2017/05/07
[#81048] Re: [ruby-cvs:65788] normal:r58614 (trunk): rb_execution_context_t: move stack, stack_size and cfp from rb_thread_t — SASADA Koichi <ko1@...>
It causes compile error on raspi 3.
3 messages
2017/05/09
[#81201] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle — "U.NAKAMURA" <usa@...>
Hi, Eric
4 messages
2017/05/16
[#81202] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle
— Eric Wong <normalperson@...>
2017/05/16
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#81427] Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534) — SASADA Koichi <ko1@...>
Hi,
6 messages
2017/05/28
[#81428] Re: Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534)
— Eric Wong <normalperson@...>
2017/05/28
SASADA Koichi <ko1@atdot.net> wrote:
[ruby-core:81320] [Ruby trunk Feature#13551] Add a method to alias class methods
From:
shevegen@...
Date:
2017-05-21 17:33:39 UTC
List:
ruby-core #81320
Issue #13551 has been updated by shevegen (Robert A. Heiler). Martin showed this example: > class Array > class << self > alias :my_new :new > end Ruby allows this flexibility, this is true. This is also great, we love it. But when you use this code and want to distribute it, it is more cumbersome. And not everyone likes to have modifications that are non-standard ruby in their code. I understand that the ruby team wants to be conservative and not proliferate with lots of extra methods that have only a special case (say active* gems), but to me I also completely understand Joshua Stowers here - if possible it is MUCH, much better when it would be in main ruby. So that everyone could use it. - I may use it if it is in ruby core/stdlib. - I may use duck patching (sometimes people use the monkey rather than the duck) for my local code. - But it is VERY unlikely that I would modify a core class of ruby like this AND distribute my code to other people too. I just consider it too cumbersome (and refinements, while the idea is ok, I never really liked the syntax... and it felt awkward... but this is for another discussion, lots of time towards ruby 3.x I hope). ---------------------------------------- Feature #13551: Add a method to alias class methods https://bugs.ruby-lang.org/issues/13551#change-65007 * Author: JustJosh (Joshua Stowers) * Status: Feedback * Priority: Normal * Assignee: * Target version: ---------------------------------------- There doesn't seem to be an intuitive way to alias class methods. Perhaps we can add a method such as ~~~ ruby alias_class_method :new_name, :old_name ~~~ -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>