(I am not sure how many of the lists you sent to allow cross-posting, I have not seen this on ruby-core, yet, and I'm not on dev@jruby).
Tony Arcieri <[email protected]> wrote: > There are changes I'd like to see happen before such a standardization > occurs. However, I'd like to gauge interest about incorporating this sort > of API into the core of the Ruby language itself before that happens. > > What do you all think about incorporating nio4r into Ruby itself? I am mildly against this, as it would likely hinder the adoption/evolution of better[1] non-blocking I/O libraries better-suited for use with multi-threaded applications. [1] Mainly, exposing one-shot notifications (via EV_ONESHOT and EPOLL_ONESHOT in kqueue and epoll respectively) to make multi-threaded programming much easier and safer (without needing userspace locks, even!). -- -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected] --- You received this message because you are subscribed to the Google Groups "rubinius-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
