Open radeusgd opened 6 months ago
I suspect that's because the runner's runRepl
does not have .strictErrors(true)
setting when creating the context.
Takeaways:
strictErrors(true)
be enabled for the REPL as well?strictErrors
? Or should we at least rename this setting to more clearly denote what it actually does by calling it interactiveMode
instead?
As shown in the repro:
We can see that the
write
operation returns a dry-run file, meaning that the Context is not enabled.I get the same behaviour without the launcher, i.e. running
.\built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\bin\enso --repl
.Interestingly, if I run a custom file with a REPL breakpoint:
it actually works correctly: