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
We get awkward semi-colons that appear at the start of the error message:
haoyi-mbp:~ haoyi$ amm Foo.sc
Foo.sc:2: not found: value rintln
;valres_1= rintln("foooo")
^CompilationFailed
This is probably an artifact of the way we preprocess the scripts in order to add the val res prefixes and stuff; we should be able to do it without adding these awkward semi-colons.
The text was updated successfully, but these errors were encountered:
… join statements, since they're no longer necessary. Fixes#439
- Also fix the ImportSplitter parser that ImportHooks use, which was incorrectly marking the end location of trailing magic imports, creating incorrect preprocessed Scala code that relied on the synthetic semicolons in order to compile and run. This should also improve the accuracy of error-reporting in these cases
Currently, given this script
We get awkward semi-colons that appear at the start of the error message:
This is probably an artifact of the way we preprocess the scripts in order to add the
val res
prefixes and stuff; we should be able to do it without adding these awkward semi-colons.The text was updated successfully, but these errors were encountered: