From: normalperson@...
Date: 2015-07-04T05:33:36+00:00
Subject: [ruby-core:69871] [Ruby trunk - Feature #11331] [Open] [PATCH] load.c: use fstring for loaded features and expanded load path

Issue #11331 has been reported by Eric Wong.

----------------------------------------
Feature #11331:  [PATCH] load.c: use fstring for loaded features and expanded load path
https://bugs.ruby-lang.org/issues/11331

* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Loaded features is an obvious candidate for fstring since
feature paths of Ruby sources are included in iseq locations,
and iseq locations are in the fstring table anyways.

Deduplicating expanded load path can reuse old objects, since
repeated expansions may get reused before old expanded paths are GC-ed
away.

Only lightly-verified since I don't have a lot of code, but seems obvious
enough.  Folks with bigger codebases are encouraged to double-check results.


---Files--------------------------------
0001-load.c-use-fstring-for-loaded-features-and-expanded-.patch (1.73 KB)


-- 
https://bugs.ruby-lang.org/