12:40 <Putonlalla> I read through the documentation of `dynamic-require` and tried to use it, but could not dynamically load every provided definition of a module into the current namespace, which is what `require` does. How do you actually dynamically `require`?

14:11 <Putonlalla> What I'm actually trying to do is create a sequence of dependent submodules from which I can load all the definitions up to a certain point.

15:24 <samth> Putonlalla: you might want `namespace-require`

15:34 <Putonlalla> It looks promising, but gives me `unbound identifier` errors.

15:44 <Putonlalla> That is, `(require (submod "modules.rkt" m))` works, while `(for-each (lambda (m) (namespace-require `(submod "modules.rkt" ,m))) (list 'm))` does not. Perhaps it needs some kind of anchor outside the `for-each`.

15:54 <samth> which identifier is unbound?

15:54 <Putonlalla> Anything provided by `m`.

16:05 <samth> are you eval'ing it in the relevant namespace?

16:06 <samth> can you provide an example that I can try?

16:06 <Putonlalla> I'm not using `eval` at all. That might be the problem.

16:15 <samth> then what did you mean about the current namespace? namespaces are a construct used with eval

16:16 <samth> Racket does not have a way to bind in a program names determined at runtime (except in the top-level, which is fundamentally a wrapper around eval)

16:16 <Putonlalla> Oh.

16:19 <Putonlalla> How do you use `eval` to implement `require` then?

16:36 <Putonlalla> My actual problem is that `module->exports` stops working when I put it in a sandbox, and I have no idea why, so I'm trying to implement these basic things to understand how they work.

16:36 <Putonlalla> The documentation is quite useless for this purpose, because it doesn't contain enough information to infer how things are going to work when you run them. There are no links to source code or formal semantics either.

16:44 <Putonlalla> A sentence like "absolute and relative module paths form a torsor with the following operations" would be immensely more helpful than the prose and incomplete examples we currently have, and would most likely also lead to a more coherent api.

19:18 <samth> Putonlalla: I don't know what it means to implement require in terms of eval

19:19 <samth> if you're using eval, then you can just `(eval '(require foo))`

19:19 <samth> if what you want is to call some API that binds identifiers, then Racket very intentionally does not provide anything that does that

19:27 <samth> in general if you want to use `(module->exports m)` just doing `(dynamic-require m (void))` as the example in the docs suggests, should be enough

19:27 <samth> but if you can give an example then I can help more