[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
[email protected] wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
[email protected] wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
From:
Eric Wong <normalperson@...>
Date:
2018-02-20 09:06:54 UTC
List:
ruby-core #85686
[email protected] wrote: > May I add two new candidates (IoThread and Thread::Coop)? Thanks for the ideas. I like Thread::Coop; maybe "Thread::Coro" is good, too... I don't think IoThread is good if we support Queue/Mutex/... Also, what do you think about having a way to pass options to thread creation like pthread_attr_t? ``` attr = Thread::Attr.new # similar to pthread_attr_setscope. I'm used to NPTL and # LinuxThreads only having PTHREAD_SCOPE_SYSTEM and ignored # of pthread_attr_setscope until I saw it again with mjit code: attr.type = :coop # (default is :native) # for advanced users only :) attr.vm_stack_size = ... attr.machine_stack_size = ... # This API gives room for future expansion Thread::Attr#create becomes a substitute for Thread.new attr.create(*args) # => Thread or Thread::Coop ``` And maybe we unify Thread::Coop and existing "Thread" as single public "Thread" class to Ruby API; similar to what we do with "Integer" (vs Bignum/Fixnum) Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
