recent change kinda breaks lexical scope with multiple modules about janet HOT 2 CLOSED

This change has been reverted and replaced with a better tool *module-make-env* which is used to dynamically construct the default environment when using require, import, and dofile.

On latest master, new usage would be like so:

main.janet

(def new-env (make-env))
(put new-env *module-cache* @{})
(put new-env *module-loading* @{})
(put new-env *module-make-env*
  (fn get-new-derived-env [&]
    (def e (make-env new-env))
    (put e :extra-stuff "hello, world")
    e))
(dofile "./my-custom-plugin.janet" :env new-env)

my-custom-plugin.janet

(import ./lib) # lib will be loaded with environment table created by get-new-derived-env

lib.janet

(print (dyn :extra-stuff)) # prints "hello, world"

from janet.

FWIW, bakpakin made the following comment here:

EDIT:
As a work around for all recent Janet versions, you can also do (import ./other :env (make-env (curenv))). The default was that import, require, and dofile start with a pristine environment, including dynamic bindings when imported. We might want to go back to that.

I didn't quite follow, but I got the sense he thought some kind of reversion might be in order.

from janet.