Scala 3 minimal support #1355
Scala 3 minimal support #1355
Conversation
| "io_bazel_rules_scala_scala_interfaces", | ||
| "io_bazel_rules_scala_scala_tasty_core", | ||
| "io_bazel_rules_scala_scala_asm", | ||
| # "io_bazel_rules_scala_scala_reflect", |
There was a problem hiding this comment.
Do we need this commented line?
|
one thing that isn't clear to me is how this interacts with ijar. I don't know the role of tasty in scala 3. I think we should document how this is working. My fear is that we are making ijars, but actually scala 3 is reading tasty files and not actually using the ijar anyway, so we are only complicating matters and hurting things. But this could be wrong. What I think we want ideally, is for tasty to support the idea of compilation interfaces, and have a scala specific way to do something like |
|
ijar should keep tasty files (bazelbuild/bazel@1489f0f) - I haven't verified if this works though. |
|
but if you retain the entire tasty file, doesn't that retain the entire AST? So, doesn't that kill the point of ijar for scala (i.e. any change to the implementation will still cause a downstream recompilation?) And if any change causes a downstream recompilation, then you might as well use a transitive compilation classpath so you minimize confusing issues with symbols being missing. |
That's correct. There's plenty of work to be done to get full support for Scala 3. |
3 participants
This adds minimal support for Scala 3:
Also added a simple Scala 3 workspace example to validate the changes, while the rest of Rules Scala tests are not fixed to work with Scala 3.
Issue #1269
Thanks @cocreature for the initial work