[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60720] [ruby-trunk - Feature #6083] Hide a Bignum definition
From:
matz@...
Date:
2014-02-14 07:59:03 UTC
List:
ruby-core #60720
Issue #6083 has been updated by Yukihiro Matsumoto. Even though this breaks source compatibility, it is worth changing it (to mark dangerous operation). So go ahead. Matz. ---------------------------------------- Feature #6083: Hide a Bignum definition https://bugs.ruby-lang.org/issues/6083#change-45142 * Author: Koichi Sasada * Status: Assigned * Priority: Normal * Assignee: Yukihiro Matsumoto * Category: * Target version: Next Major ---------------------------------------- Now, the struct RBignum which is a definition of Bignum in C is located in include/ruby/ruby.h. It means we can't change implementation of Bignum. For example, using GMP as Bignum representation. I propose to move the struct RBignum definition from include/ruby/ruby.h to bignum.c. I believe no one use struct RBignum directly (except core). It has possibility to break binary compatibility. ---Files-------------------------------- hide-bignum-internal.patch (4.66 KB) -- http://bugs.ruby-lang.org/