Nice, so I am thinking it now in terms of pipable repl exposing to the world only two streams, one in and one out. Each one is responsible for evaluating its part of the stream without exposing parser and eval, and the terminal of this exhaust system is stdout 😀
I mean no rocket science here I know 😀 However there are fewer things to add to the unrepl protocol if the only communication medium between repls are pipes
I probably now get in full what you had in mind all along 😅
Yeah maybe. And upgrading a repl is just the matter of sending a specific input.
yep the protocol stays the same, the "engine" can just pipe the streams when an upgrade is requested
All this upgrade stuff vaguely reminds me of Alan Kay and alien "objects".
Ah. I may have found a way to solve the "async eval" problem without committing to a dynvars impl. Yet another indirection:-)
1👍21