Module:;eval_ast_as_new defaults to merging namespaces.

doc/src/language/fn-namespaces.md

@@ -88,84 +88,3 @@ fn say_hello() {
 }
 say_hello();
 ```
-
-
-Namespace Consideration When Not Using `FileModuleResolver`
----------------------------------------------------------
-
-[Modules] can be dynamically loaded into a Rhai script using the [`import`] keyword.
-When that happens, functions defined within the [module] can be called with a _qualified_ name.
-
-The [`FileModuleResolver`][module resolver] encapsulates the namespace inside the module itself,
-so everything works as expected.  A function defined in the module script cannot access functions
-defined in the calling script, but it can freely call functions defined within the same module script.
-
-There is a catch, though.  When using anything other than the [`FileModuleResolver`][module resolver],
-functions in a module script refer to functions defined in the _global namespace_.
-When called later, those functions may not be found.
-
-When using the [`GlobalFileModuleResolver`][module resolver], for example:
-
-```rust
-Using GlobalFileModuleResolver
-==============================
-
------------------
-| greeting.rhai |
------------------
-
-fn get_message() { "Hello!" };
-
-fn say_hello() {
-    print(get_message());           // 'get_message' is looked up in the global namespace
-                                    // when exported
-}
-
-say_hello();                        // Here, 'get_message' is found in the module namespace
-
----------------
-| script.rhai |
----------------
-
-import "greeting" as g;
-g::say_hello();                     // <- error: function not found - 'get_message'
-                                    //    because it does not exist in the global namespace
-```
-
-In the example above, although the module `greeting.rhai` loads fine (`"Hello!"` is printed),
-the subsequent call using the _namespace-qualified_ function name fails to find the same function
-'`message`' which now essentially becomes `g::message`.  The call fails as there is no more
-function named '`message`' in the global namespace.
-
-Therefore, when writing functions for a [module] intended for the [`GlobalFileModuleResolver`][module resolver],
-make sure that those functions are as independent as possible and avoid cross-calling them from each other.
-
-A [function pointer] is a valid technique to call another function in an environment-independent manner:
-
-```rust
------------------
-| greeting.rhai |
------------------
-
-fn get_message() { "Hello!" };
-
-fn say_hello(msg_func) {            // 'msg_func' is a function pointer
-    print(msg_func.call());         // call via the function pointer
-}
-
-say_hello(Fn("get_message"));
-
-
----------------
-| script.rhai |
----------------
-
-import "greeting" as g;
-
-fn my_msg() {
-    import "greeting" as g;         // <- must import again here...
-    g::get_message()                // <- ... otherwise will not find module 'g'
-}
-
-g::say_hello(Fn("my_msg"));         // prints 'Hello!'
-```