You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To improve the ability to copy-paste snippets, such as compiler options.
Describe the solution you'd like
implement changes in the directives parser so that
//>usingoptions"-Xasync", "-Xfatal-warnings"
can be written as
//>usingoptions-Xasync-Xfatal-warnings
Quotes can still be used for when a value needs to include whitespace, with the same escape characters for scala strings.
Here is a larger example:
//>usingscala3.2.2//>usingtoolkitlatest//>usingoptions-Xfatal-warnings-Yexplicit-nulls-Ysafe-init-source:future//>usingdepcom.lihaoyi::cask:0.9.0//>usingsome.key"I have spaces"
We do not anticipate issues in adapting scala/vscode-scala-syntax to support the new syntax. Additionally, values are still of string type.
Describe alternatives you've considered
no alternative considered.
Additional context
Since directives will not become scala syntax, there is no need to reuse the same rules as the scala parser.
Discussed at the Scala Tooling Summit March 2023
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
To improve the ability to copy-paste snippets, such as compiler options.
Describe the solution you'd like
implement changes in the directives parser so that
//> using options "-Xasync", "-Xfatal-warnings"
can be written as
//> using options -Xasync -Xfatal-warnings
Quotes can still be used for when a value needs to include whitespace, with the same escape characters for scala strings.
Here is a larger example:
We do not anticipate issues in adapting scala/vscode-scala-syntax to support the new syntax. Additionally, values are still of
string
type.Describe alternatives you've considered
no alternative considered.
Additional context
Since directives will not become scala syntax, there is no need to reuse the same rules as the scala parser.
Discussed at the Scala Tooling Summit March 2023
The text was updated successfully, but these errors were encountered: