Skip to content

Conversation

@odersky
Copy link
Contributor

@odersky odersky commented Jan 5, 2026

It does not seem to be used anywhere and it complicates text formatting considerably.

It does not seem to be used anywhere and it complicates text formatting considerably.
@@ -1,5 +1,3 @@
//> using options -print-lines

val x: Int = "not an int" // error
Copy link
Contributor

@som-snytt som-snytt Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could just delete the file.

Maybe we should consult the print-lines community? Is there a meet-up in London for that?

Amazing simplification, of the YAGNI variety.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, that test did nothing anyway.

Copy link
Contributor

@som-snytt som-snytt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a follow-up to #14227 (comment)

... what is -print-lines supposed to do? Can we remove it? 😅

It has no effect on scalac -decompile task. The commit history hints at the maintenance burden. I regret my earlier comment that YAGNI, because now it is FOMO: will I want to see line ranges in my rich dev env of 2026? But that sounds like a downstream tooling issue.

@odersky odersky merged commit 223d1bb into scala:main Jan 7, 2026
95 of 96 checks passed
@odersky odersky deleted the revise-texts branch January 7, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants