* [ruby-core:69871] [Ruby trunk - Feature #11331] [Open] [PATCH] load.c: use fstring for loaded features and expanded load path
[not found] <redmine.issue-11331.20150704053332@ruby-lang.org>
@ 2015-07-04 5:33 ` normalperson
0 siblings, 0 replies; only message in thread
From: normalperson @ 2015-07-04 5:33 UTC (permalink / raw)
To: ruby-core
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-07-04 5:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-11331.20150704053332@ruby-lang.org>
2015-07-04 5:33 ` [ruby-core:69871] [Ruby trunk - Feature #11331] [Open] [PATCH] load.c: use fstring for loaded features and expanded load path normalperson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).