Jackson Loper

1. Simple max-printout flag like that would be great! Could it possibly be set from within the interpreter, perhaps through some global variable? 2. Another (hopefully quick?) fix would be...

Mimer sounds awesome. Do that.

Eek! I see this is much trickier than I had hoped. We need to find somebody willing to reopen nodejs/node#1268 and get it solved :). I fear it might involve...

I guess #137 might help a bit, if it could get merged? Any hope for that anytime soon?

is this still an issue? i'm certainly still experiencing it? confused about what the solution is.

I'm a huge fan of this (especially a jupyter kernel, that would be wow!), but I'm confused about what the desired behavior of such a REPL would be. For one...

I guess the biggest confusion I'm having is that _every let declaration in a function corresponds to a new memory slot in the stack frame_. I don't see how that...

"New memory slot for every let" is definitely correct, and as it should be! I agree. But I don't see how it works for a repl. That's exactly why the...

I quite agree -- the repl shouldn't change rust semantics!! (The matter of the unexpected out-of-order deallocation of shadowed variables is a really a topic for another issue. At this...

I like your "repl history == function body" example! It's wonderfully explicit, and I think it would be very clear for users. I'm not exactly sure how it would generalize...