Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repl pick up where you left off after crash #9791

Open
scabug opened this Issue May 25, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@scabug
Copy link

scabug commented May 25, 2016

Probably folks have seen the crash message in REPL:

That entry seems to have slain the compiler.  Shall I replay
your session? I can re-run each line except the last one.
[y/n]
Abandoning crashed session.

I had a version once that asked [y/n/q] to quit directly, and save keystrokes. But now I wonder, is it better just to say, Type :replay to re-run each line except the last. I have a separate idea for :replay -all -Xprint:typer to also replay the last line.
That means if they don't replay, then reset before continuing.

Retronym: What we really ought to do is start a new compiler with the compilation products of the crashed compiler on the classpath. Should be no need to replay.
The tab completion works in this way every time you hit TAB.

Also Retronym: We could even have a mode of the REPL that uses a new Global for every line.

@scabug

This comment has been minimized.

Copy link
Author

scabug commented May 25, 2016

Imported From: https://issues.scala-lang.org/browse/SI-9791?orig=1
Reporter: @som-snytt
Affected Versions: 2.12.0-M3

@scabug

This comment has been minimized.

Copy link
Author

scabug commented Aug 10, 2016

@som-snytt said:
One idea is to have a separate github repo for "community" contributions, using github issues. That would keep the scala PR queue shorter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.