Michał Pałka
Michał Pałka
I started working on the parsers. At least for now I have found out that that there's no infinite loop but the compilation time grows very quickly when a rule...
I'm getting a similar error but it's not specific to packaging in my case Given a scala file, e.g. ```scala // Tmp.scala object Foo ``` when on JVM 8 ```shell...
In scala 3 if you write your init script like this ```scala export Hello.* ``` and you run `scala-cli repl InitScript.scala` then in REPL you can already directly access everything...
I've found one limitation of my solution: wildcard exports work correctly with objects but not with packages.
Maybe scala-cli could have a command for switching between basic and advanced mode? That would be more convenient than having to pass a flag every time an advanced command is...
I wouldn't like to go too far but we should probably keep in mind that using this exact syntax could cause some complications if we wanted to have some kind...
Also if we finally decide to use internal string interpolation we should make sure that it's well supported by IDEs so that it's properly highlighted and people don't get interpolation...
One thing to consider (although making things more complicated): should we allow some kind of (predefined and OS agnostic?) path variables, e.g. `HOME` or `TMP`?
@abgruszecki could you confirm this should actually work?
I can confirm getting a compilation error with 3.2.2-RC1-bin-20220916-afc6ce4-NIGHTLY