You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2018. It is now read-only.
Emscripted languages can call exit() which will raise a JS error and might render the interpreter non-functional. Currently we just print the exception as an internal error and continue as if nothing happened. Instead we should provide a way to hook into this call (e.g. via an exit event) so that clients can properly respond to exiting the interpreter. E.g. for repl.it that might mean printing an exit message and not restarting the prompt, or returning to the languages selector.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Emscripted languages can call
exit()
which will raise a JS error and might render the interpreter non-functional. Currently we just print the exception as an internal error and continue as if nothing happened. Instead we should provide a way to hook into this call (e.g. via anexit
event) so that clients can properly respond to exiting the interpreter. E.g. for repl.it that might mean printing an exit message and not restarting the prompt, or returning to the languages selector.The text was updated successfully, but these errors were encountered: