scala-dev
scala-dev copied to clipboard
scala
Improve line number information
Ensure that standard line number information is kept when inlining from the same file, eliminated otherwise. Write tests.
Next step: add support for JSR-45 debugging info, which allows
- line numbers of multiple source files within one classfile
- full (project-relative?) path of source file, not only the file name, should help debuggers in when not using Java's package/directory convention for sources
btw, we already (in ensime) handle the source file lookup issue in ensime using our indexer.
Does this JSR-45 support include information such as expanding line numbers to source ranges? The problem faced when writing a debugger is that we only get line number info, but we want to highlight the block of code (rangepos) that is being evaluated.
Of course, stacktrace demangling is another issue...
This has gone a bit cold, could somebody please help me with technical input to write a proposal?
GSoC needs a mentor, which would be hard for this. We also have a debugging proposal already :-)
Scala Center is ideal for this if Lightbend's customers aren't prepared to directly fund it, because it really needs somebody working closely with EPFL or core scala team.
I've put together a draft SC proposal here if anybody has any comments: https://gist.github.com/fommil/1867119e7f184d36342bd5e4b34c7bfe
Scala Center proposals in this area:
- SCP-011 was accepted in 2017, but never really happened
- SCP-022 proposes resuming work on it (and targeting Scala 3 as well)
further on SCP-022: https://contributors.scala-lang.org/t/improving-the-scala-debugging-experience/4264
cc @errikos, who might not know about this ticket
@errikos does your work on JSR 45 (https://github.com/scala/scala/pull/9121) cover this as well, do you think?
Hello. Sorry for the late reply.
Yes, it covers both bullets. For the second one, we store the fully qualified class name, so not project relative path exactly.
