Imported From: https://issues.scala-lang.org/browse/SI-7919?orig=1
Reporter: @densh
Affected Versions: 2.11.0-M6

@paulp said (edited on Oct 26, 2013 7:05:28 PM UTC):
Reduced. It's losing the newline token after a completely empty interpolated string. If it's s"1", or a semicolon instead of a newline, or two newlines, or a comment after the empty string, it compiles.

class A {
  s""
  5
}

@densh said (edited on Jan 24, 2014 5:34:04 PM UTC):
I've spend this day running the Scanner through debugger. The only thing I've found out it that the failure to insert the semicolon is caused by afterLineEnd() call on line https://github.com/scala/scala/blob/master/src/compiler/scala/tools/nsc/ast/parser/Scanners.scala#L332. This call fail to return true on the last string interpolation token and thus semicolon isn't inserted after it. The function itself is based on dozen of mutable variables that appear to be out of sync in that particular case https://github.com/scala/scala/blob/master/src/compiler/scala/tools/nsc/ast/parser/Scanners.scala#L372. A number of mutable variables involved seem to be beyond my limit of code comprehension. Maybe somebody else will have a better luck with it.

@som-snytt said:
To detect triple-quotes, it's using CharArrayReader.nextRawChar instead of nextChar, so it's not detecting "potentialLineEnd".

@som-snytt said:
scala/scala#3411

@densh said:
THANK YOU

@som-snytt said:
Quasiquotes are thanks enough.

This was a quickie because I'd just looked at that other EOL bug.