[#79440] [Ruby trunk Bug#13188] Reinitialize Ruby VM. — shyouhei@...
Issue #13188 has been updated by Shyouhei Urabe.
6 messages
2017/02/06
[#79441] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
— SASADA Koichi <ko1@...>
2017/02/06
On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote:
[#79532] Immutable Strings vs Symbols — Daniel Ferreira <subtileos@...>
Hi,
15 messages
2017/02/15
[#79541] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/15
Em 15-02-2017 05:05, Daniel Ferreira escreveu:
[#79543] Re: Immutable Strings vs Symbols
— Daniel Ferreira <subtileos@...>
2017/02/16
Hi Rodrigo,
[#79560] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/16
Em 15-02-2017 22:39, Daniel Ferreira escreveu:
[ruby-core:79405] Re: [ruby-changes:45397] normal:r57469 (trunk): io.c: recycle garbage on write
From:
SASADA Koichi <ko1@...>
Date:
2017-02-03 05:58:52 UTC
List:
ruby-core #79405
On 2017/01/31 18:18, Eric Wong wrote: > 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. My question is "are there any other way for this purpose?". Because of using flags, I think we "all of string.c hacker" should know this flag. My another question is, is this flag technique is valuable to pay this effort for all string.c hackers? ---- Maybe I need to read it... (Honestly, I can't read it enough) -- // SASADA Koichi at atdot dot net Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>