Bug #15206: require_relative in std_lib

• Status: Open
• Priority: Normal
• Assignee: -
• Target version: -
• Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN

[marcandre (Marc-Andre Lafortune)]

I noticed that there are some require for internal files in lib/. Ideally, they would be using require_relative instead. This is faster and more explicit.

Note: require_relative had a potential issue with symlinks that was fixed in 2.5, so libraries that might be loaded from earlier Ruby, like rubygems, can not yet be updated.

I've created a PR and would like to know if there are comments / objections / things I'm missing.

[MSP-Greg (Greg L)]

The Appveyor run on the PR passed.

Appveyor testing has been intermittently failing. With parallel/multi testing (test-all and/or test-spec), there can be a lot more files being checked and possibly loaded. Considering more than one CI VM may be exist on a system, and they may share drives, anything that lowers disk I/O is good.

[shyouhei (Shyouhei Urabe)]

• Is duplicate of Feature #8781: Use require_relative() instead of require() if possible added