I found one hole, that the resettable-ness helps w...

# scripting

[apatrida]

I found one hole, that the resettable-ness helps with. If you compile then eval and the eval has a runtime exception, it isn’t added to the history (compiledLoadedClassesHistory) and it really can’t be anyway but that means you can’t eval again after because of history mismatch. So for the compileAndEval case I can handle it, and if someone calls the individual components themselves they’ll need to handle it. In the atomic case I just reset the compiler back to the previous line assuming this line is the latest on the stack