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
Wrong line number information in bytecode #6288
Comments
Imported From: https://issues.scala-lang.org/browse/SI-6288?orig=1 |
@dragos said: |
@retronym said: |
@retronym said (edited on Dec 11, 2012 11:02:13 AM UTC):
Looks like dereferencing the scrutinee is wrongly positioned: {noformat}[136][136]Case3.unapply([115]x1);{noformat} |
@retronym said: I'll see if I can find any others. |
@retronym said: |
Positions of translated patterns (and consequently line numbers in bytecode) are sometimes wrong. While things are significantly better than in 2.9, there are still issues with unapplies. In this example, notice that in the last case some temporary variable loads are positioned at the
match
position (and the return statement as well).This causes the debugger to jump between the current line and the beginning of the match for those steps and it is very confusing. I think this is a low-hanging fruit that can improve the user experience a lot.
the output:
The interesting bits are at offset 84 and 87 and further down.
The text was updated successfully, but these errors were encountered: