[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71343] Re: [Ruby trunk - Feature #8976] file-scope freeze_string directive
From:
KOSAKI Motohiro <kosaki.motohiro@...>
Date:
2015-11-05 03:00:12 UTC
List:
ruby-core #71343
> Shugo Maeda wrote:
>
>> It's not just for compatibility.
>>
>> The original problem was that a new String object has to be allocated by a string literal
>> for each evaluation. So I don't understand the reason why a dynamic string literal should
>> be frozen in spite of the fact freezing dynamic strings can't reduce object allocation.
>
> It is not a big problem.
> We can reduce extra object allocation with "foo#{exp}bar".dup using an optimization similar for "foo".freeze.
>
> I think the pragma and option name should explain the behavior.
> The name is "frozen-string-literal".
> So, basically, all string literal should return a frozen object.
>
> We need an explanation if we introduce an exception.
+1
Current explanation is too weak to make an exception, I think.