Scala 2 team issues. Not for user-facing bugs or directly actionable user-facing improvements. For build/test/infra and for longer-term planning and idea tracking. Our bug tracker is at https://github.com/scala/bug/issues
This is an imple proposal for @ckipp01's Roadmap for actionable diagnostics, which will enable Scala compiler to suggest (semi-automatic) code edits together with compilation errors and warnings, likely useful for things like deprecation and migration warnings.
Scala 2.x compiler bridge is now capable of sending Problem#actions since https://github.com/sbt/zinc/pull/1186. As a toy example, it scans for "procedure syntax is deprecated:" in the error message to generate an action.
Hopefully none. The errors and warning message should remain as-is including code examples. Actions will be additional information that compatible editors like IntelliJ and Metals can consume.
This is an imple proposal for @ckipp01's Roadmap for actionable diagnostics, which will enable Scala compiler to suggest (semi-automatic) code edits together with compilation errors and warnings, likely useful for things like deprecation and migration warnings.
What's been added to Zinc thus far
Problem#actions
- https://github.com/sbt/sbt/blob/v1.9.0-RC3/internal/util-interface/src/main/java/xsbti/Problem.java#L81-L83 (Action contains WorkspaceEdit, which contains TextEdit)Problem#actions
since https://github.com/sbt/zinc/pull/1186. As a toy example, it scans for"procedure syntax is deprecated:"
in the error message to generate an action.What I'd like to add to Scala 2.13
Action
,WorkspaceEdit
, andTextEdit
(trait in api + data type in internal).val
infor
comprehension https://github.com/scala/scala/pull/6348Impact to existing users
Hopefully none. The errors and warning message should remain as-is including code examples. Actions will be additional information that compatible editors like IntelliJ and Metals can consume.