ruby-core

normalperson@yhbt.net wrote:

(2014/02/01 18:19), Eric Wong wrote:

rasch@raschnet.com wrote:

There are a number of reasons I use them, but the most obvious is that a

On 6 February 2014 20:22, Eric Wong <normalperson@yhbt.net> wrote:

Thanks, committed as r44869.

I cannot reproduce the problem on r44870 (x86_64-linux)

Interesting. Have you contacted the Passenger developers about this?

We have a mailing list (ruby-core) where matz and other core developers

Anybody can join and post to the ruby-core mailing list, not just

We are working on official faq, maybe we can have another that is meant for developers.

I suggest using a coverage struct pointer in rb_iseq_struct to hold all

akr@fsij.org wrote:

waghanza@gmail.com wrote:

(2014/02/13 19:04), Eric Wong wrote:

array.c: volatile in rb_ary_each along with the explanation in r32201 is

Eric Wong <normalperson@yhbt.net> wrote:

akr@fsij.org wrote:

sam.rawlins@gmail.com wrote:

Hi, all

ngotogenome@gmail.com wrote:

fabio (and anybody else for future reference):

The yahns HTTP server uses a long-lived fdmap array to map

ko1: may I commit the removal of special case for large array/hash?

sam.rawlins@gmail.com wrote:

I finally tried commit eaadf820633e74350404d009a1c251f6319454aa

(2014/02/28 16:44), normalperson@yhbt.net wrote:

nobu@ruby-lang.org wrote:

nobu@ruby-lang.org wrote:

Trivial addendum for v3 (pushed earlier, but I lost my Internet