Fork me on GitHub
#unrepl
<
2017-05-31
>
cgrand12:05:01

At last, my cljs repl is upgradable anew and I have some dyn env handling to tighten

pesterhazy13:05:04

is there something I can play with already?

cgrand13:05:35

you can clone the repo, and follow the README, that’s all

cgrand13:05:13

why 🐊 ?

pesterhazy13:05:26

strong as a crocodile

pesterhazy13:05:37

it's a pretty cool animal

pesterhazy13:05:30

I checked it out, it works well

cgrand13:05:04

pesterhazy: on upgrade there’s an extra prompt from the upgraded repl, it’s a bug

pesterhazy13:05:48

So the idea would be to ship something like cljs-js-repl with lumo. That's the minimum code required for a client to upgrade itself.

pesterhazy13:05:57

(just thinking out loud here)

cgrand13:05:18

that’s the idea

cgrand13:05:33

eval in cljs-js has an async API (in practice lumo and planck impls are sync... for now)

cgrand13:05:51

(one can simulate async by adding a setTimeout)

pesterhazy13:05:29

really like the ideaa

cgrand15:05:18

Right before the daycare pickup break, I was talking about async eval.

cgrand15:05:39

So the problem is that when the evaluation really happen the current set of bindings may not be in place anymore. So *in* for example wouldn't point to the input of the repl :-/

cgrand15:05:04

So short of having a global dynamic var solution, eval could offer a way to switch dynamic environments. It may be a simple function… passed as a dynamic variable.