-
Notifications
You must be signed in to change notification settings - Fork 176
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
Scala doesn't work #209
Comments
Documentation:
Corresponding
|
How hilariously Java. |
With Braden's pull request:
It doesn't seem to respond to input properly, and running it with scripts as an argument yields
Expected behavior:
So there's still work to be done! |
The JLine error is expected, see ab79a98. Scala should probably handle it better, but that's not really our fault. |
Yeah, but input doesn't seem to get evaluated at all. |
The REPL is so close to working!
|
Using the Java 8 version, we're very close to working. REPL would work if the compiler worked...
I believe the below issue is caused solely by #159, which separates bootstrap-loaded classes from the application-loaded classes. Normally, all of the Scala JAR files are on the bootstrap classpath, which our command line parser doesn't support (it has weird syntax). |
Tried the newest version of Scala in the
Lamesauce. |
Hmm, it works sometimes?
|
Hmm, now I can't reproduce the earlier failure. Interesting. Well, I guess Scala works (slowly) in
|
Scala currently works (slowly) in the master branch, as indicated above. |
It looks like we are very close to having the Scala repl working; perhaps one native method away:
The text was updated successfully, but these errors were encountered: