<@U0CHHN4F4> looking back on the problem of "compi...

# scripting

[apatrida]

@ilya.chernikov looking back on the problem of "compileAndEval(A), compileAndEval(B) which fails with compiler error, compileAndEval(C) causes crash" ... this is because the state.getNextLineNo uses the same line number again for the 3rd step. Something isn't cleaned up, so the line number must increment. But if you do that outside in your wrapper layer, and you reset back to a line, you have to then manage that everything is kept in sync. I guess your line number doesn't really need to be contigous, the atomic could go up even after a reset because it clears history and doesn't need to really change the line number.