[#28687] [Bug #2973] rb_bug - Segmentation fault - error.c:213 — rudolf gavlas <redmine@...>

Bug #2973: rb_bug - Segmentation fault - error.c:213

10 messages 2010/03/16

[#28735] [Bug #2982] Ruby tries to link with both openssl and readline — Lucas Nussbaum <redmine@...>

Bug #2982: Ruby tries to link with both openssl and readline

16 messages 2010/03/18

[#28736] [Bug #2983] Ruby (GPLv2 only) tries to link to with readline (now GPLv3) — Lucas Nussbaum <redmine@...>

Bug #2983: Ruby (GPLv2 only) tries to link to with readline (now GPLv3)

10 messages 2010/03/18

[#28907] [Bug #3000] Open SSL Segfaults — Christian Höltje <redmine@...>

Bug #3000: Open SSL Segfaults

19 messages 2010/03/23

[#28924] [Bug #3005] Ruby core dump - [BUG] rb_sys_fail() - errno == 0 — Sebastian YEPES <redmine@...>

Bug #3005: Ruby core dump - [BUG] rb_sys_fail() - errno == 0

10 messages 2010/03/24

[#28954] [Feature #3010] slow require gems in ruby 1.9.1 — Miao Jiang <redmine@...>

Feature #3010: slow require gems in ruby 1.9.1

15 messages 2010/03/24

[#29179] [Bug #3071] Convert rubygems and rdoc to use psych — Aaron Patterson <redmine@...>

Bug #3071: Convert rubygems and rdoc to use psych

10 messages 2010/03/31

[ruby-core:28476] Re: [Feature #905] Add String.new(fixnum) to preallocate large buffer

From: Yusuke ENDOH <mame@...>
Date: 2010-03-04 17:28:49 UTC
List: ruby-core #28476
Hi,

2010/3/5 Kornelius Kalnbach <murphy@rubychan.de>:
> Doesn't Ruby allocate already using a "double memory if you run out"
> rule? That makes string concatenation (amortized) linear, even if the
> string must be moved in the memory.

Yes, it does.  This is why I think experiment is needed.

Because the suggested feature can be used to omit first some
expansions, it will actually reduce time.  But I guess if the
reduced time is not so much.


> Even with this API extension, we wouldn't have control over the
> generation of the string buffer in many use cases, as in Array#join,
> String#% or in literals using #{}. Its use would be limited to String#<<.

Absolutely.  The feature is hard to use.
Even if we pre-allocated a string, calling some method on the
string may shrink it.

I think we should call the feature just "optimization hint"
rather than API.  It is better to think the hint may be even
ignored.

-- 
Yusuke ENDOH <mame@tsg.ne.jp>

In This Thread