[ruby-core:65380] [ruby-trunk - Feature #10320] [Open] require into module

Issue #10320 has been reported by So Wieso.

----------------------------------------
Feature #10320: require into module
https://bugs.ruby-lang.org/issues/10320

* Author: So Wieso
* Status: Open
* Priority: Normal
* Assignee:=20
* Category: core
* Target version:=20
----------------------------------------
When requiring a library, global namespace always gets polluted, at least w=
ith one module name. So when requiring a gem with many dependencies, at lea=
st one constant enters global namespace per dependency, which can easily ge=
t out of hand (especially when gems are not enclosed in a module).

Would it be possible to extend require (and load, require_relative) to put =
all content into a custom module and not into global namespace?

Syntax ideas:
<code>
require 'libfile', into: :Lib   # keyword-argument
require 'libfile' in Lib   # with keyword, also defining a module Lib at cu=
rrent binding (unless defined? Lib)
require_qualified 'libfile', :Lib
</code>

This would also make including code into libraries much easier, as it is we=
ll scoped.
<code>
module MyGem
=C2=A0=C2=A0require 'needed' in Need

=C2=A0=C2=A0def do_something
=C2=A0=C2=A0=C2=A0=C2=A0Need::important.process!
=C2=A0=C2=A0end
end
 # library user is never concerned over needed's content
</code>
Some problems to discuss:
=E2=80=A3 requiring into two different modules means loading the file twice?
=E2=80=A3 monkeypatching libraries should only affect the module =C2=AD=E2=
=86=92 auto refinements?
=E2=80=A3 maybe also allow a binding as argument, not only a module?
=E2=80=A3 privately require, so that required constants and methods are not=
 accessible from the outside of a module (seems to difficult)
=E2=80=A3 what about $global constants, read them from global scope but cop=
y-write them only to local scope?

Similar issue:
https://bugs.ruby-lang.org/issues/5643



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