[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...
Issue #13618 has been reported by normalperson (Eric Wong).
12 messages
2017/06/01
[#88695] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/08/27
> https://bugs.ruby-lang.org/issues/13618
[#81569] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
3 messages
2017/06/04
[#81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread. — sir.nickolas@...
Issue #13632 has been reported by nvashchenko (Nikolay Vashchenko).
4 messages
2017/06/05
[#81590] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures. — Eric Wong <normalperson@...>
ko1@ruby-lang.org wrote:
5 messages
2017/06/06
[#81591] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81596] Re: [ruby-cvs:66203] Re: Re: ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81825] [Ruby trunk Feature#13697] [PATCH]: futex based thread primitives — normalperson@...
Issue #13697 has been reported by normalperson (Eric Wong).
3 messages
2017/06/29
[ruby-core:81570] [Ruby trunk Feature#12739] deprecate_constant :Fixnum, :Bignum
From:
rob@...
Date:
2017-06-04 21:44:35 UTC
List:
ruby-core #81570
Issue #12739 has been updated by robertgleeson (Robert Gleeson). znz (Kazuhiro NISHIYAMA) wrote: > How about `class Object; deprecate_constant :Fixnum, :Bignum; end`? > > * naruse supports: https://twitter.com/nalsh/status/773800491671101441 > * akr objects: https://twitter.com/tanaka_akr/status/773817391218249729 > > I don't mind either way. > Do you have any comment about it? It would be nice to have `constant_deprecated?`. To avoid all of these warnings while supporting <2.4 and >=2.4 i track what constants are deprecated in an array, and then avoid using them or not by checking the array at runtime. It's bit of a pain.. ---------------------------------------- Feature #12739: deprecate_constant :Fixnum, :Bignum https://bugs.ruby-lang.org/issues/12739#change-65272 * Author: znz (Kazuhiro NISHIYAMA) * Status: Closed * Priority: Normal * Assignee: * Target version: ---------------------------------------- How about `class Object; deprecate_constant :Fixnum, :Bignum; end`? * naruse supports: https://twitter.com/nalsh/status/773800491671101441 * akr objects: https://twitter.com/tanaka_akr/status/773817391218249729 I don't mind either way. Do you have any comment about it? -- 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>