[#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:81845] Re: [Ruby trunk Feature#13434] better method definition in C API
From:
Eric Wong <normalperson@...>
Date:
2017-06-30 08:03:35 UTC
List:
ruby-core #81845
ko1@atdot.net wrote: > As I wrote before, I against this idea. My idea is to write > definitions in Ruby with special form. Sorry, I wasn't sure what you wanted the last time this came up. I guess it was around https://bugs.ruby-lang.org/issues/11339 Particularly: [ruby-core:69990] https://public-inbox.org/ruby-core/55A72930.40305@atdot.net/ I remember not liking Ricsin syntax, but maybe a Ruby API can be better than Ricsin... > Comparison: > > * Write info with C > * Easy to learn (people should know only C syntax) > * Easy to implement > > * Write info with Ruby w/ special firm > * Easy to write > * Easy to read > * Easy to learn (people should know Ruby syntax and some restrictions) (I agree it is possible that "some restrictions" will confuse people.) > * We can compile it and know all of information before running Ruby (*1) OK, I agree. <snip> excellent explanation. > Moreover, we can prepare tables. OK, I like this part. > Furthermore, we can defer converting until first method call. <snip> OK that sounds excellent! :) > ``` > > I'm suspect that most of classes are not used (think about many of Exception class) so that this kind of optimization will improve speed (reduce boot time) and memory efficiency. Yes, that would be great. However, we will take into account fork and CoW savings. Should I try to implement your table idea? Or did you already start? You are more familiar with this, but maybe I can try... In addition to improved kwarg handling for C methods, my other goal is to be able to mark read-only/use-once/const/etc. args to avoid unnecessary allocations at runtime. This will be more flexible than current optimizations (opt_aref_with, opt_aset_with, etc). Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>