[#78949] [Ruby trunk Feature#13095] [PATCH] io.c (rb_f_syscall): remove deprecation notice — kosaki.motohiro@...
Issue #13095 has been updated by Motohiro KOSAKI.
3 messages
2017/01/03
[#78997] [Ruby trunk Bug#13110] Byte-based operations for String — shugo@...
Issue #13110 has been updated by Shugo Maeda.
3 messages
2017/01/06
[#79228] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150] — Eric Wong <normalperson@...>
naruse@ruby-lang.org wrote:
5 messages
2017/01/23
[#79511] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150]
— Eric Wong <normalperson@...>
2017/02/13
Eric Wong <normalperson@yhbt.net> wrote:
[#79518] Re: [ruby-cvs:64576] naruse:r57410 (trunk): Prevent GC by volatile [Bug #13150]
— Nobuyoshi Nakada <nobu@...>
2017/02/13
On 2017/02/13 10:04, Eric Wong wrote:
[#79298] [Ruby trunk Bug#13085][Assigned] io.c io_fwrite creates garbage — nobu@...
Issue #13085 has been updated by Nobuyoshi Nakada.
3 messages
2017/01/29
[#79337] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write — SASADA Koichi <ko1@...>
Eric:
4 messages
2017/01/31
[#79352] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write
— Eric Wong <normalperson@...>
2017/01/31
SASADA Koichi <ko1@atdot.net> wrote:
[ruby-core:79352] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write
From:
Eric Wong <normalperson@...>
Date:
2017-01-31 09:18:10 UTC
List:
ruby-core #79352
SASADA Koichi <ko1@atdot.net> wrote:
> Eric:
>
> I'm not sure about implementation of IO.copy_stream but do you need to
> add this flag for *all* of T_STRING? We need to care this flag if we
> want to manipulate strings.
This flag is only set for klass==0, now. It is safe to use
for all klass (at least all tests+rubyspec pass),
but I limited it to klass==0 to avoid triggering CoW.
I don't think using this flag (FL_USER6) imposes new burdens for
anybody.
FL_USER2 was overloaded before this patch for embed vs shared
(non-embed) case. So overloading FL_USER{3..6} for
embed-vs-non-embed case should be OK, too. We still have
FL_USER{3..5} available to use with shared strings after this
change.
Maybe some weird 3rd party extension overloads FL_USER{3..6},
too but I'm not sure if we can ever support that.
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>