From: Charles Oliver Nutter <headius@...>
Date: 2011-09-09T07:07:28+09:00
Subject: [ruby-core:39386] Re: RubySpec vs CRuby's test/...

On Thu, Sep 8, 2011 at 3:57 PM, Luis Lavena <luislavena@gmail.com> wrote:
> But honestly, nobody from core really "care" to improve this on
> Windows and the few that use Ruby on Windows don't have the time to
> dig into Ruby C code and extract what is the expected behavior of Ruby
> to add to RubySpec.

This may be the biggest problem.

Matz: Is it official policy that all feature changes in Ruby must be
accompanied by a test or spec? If not, why not? If so, why aren't they
going into a non-MRI-specific test suite?

Shouldn't ruby-core help maintain an implementation-agnostic Ruby
behavioral test suite? If so, why isn't that happening, and why
couldn't it be RubySpec? If not, why not?

- Charlie