Closed armanbilge closed 7 months ago
Thanks for the reporting, I think we could even include test for that in the CI
I'm not able to reproduce the problem on MacOS with Scala-CLI 1.1.2:
% scala-cli S.scala
[warn] ./S.scala:1:11
[warn] Using 'latest' for toolkit is deprecated, use 'default' to get more stable behaviour
[warn] //> using toolkit latest
[warn] ^^^^^^^^^^^^^^
Compiling project (Scala 3.3.1, Scala Native 0.4.16)
Compiled project (Scala 3.3.1, Scala Native 0.4.16)
[info] Linking (677 ms)
[info] Checking intermediate code (quick) (77 ms)
[info] Discovered 701 classes and 3844 methods
[info] Optimizing (debug mode) (602 ms)
[info] Generating intermediate code (493 ms)
[info] Produced 12 files
[info] Compiling to native code (1536 ms)
[info] Total (3481 ms)
hello world
Yes, this will no longer be reproducible because scala-cli has released several new versions that upgrade the Scala Native toolchain and meanwhile toolkit has not released anything new. But it could happen again unless there is a plan so it won't happen again. In the Typelevel Toolkit we build a small app against the latest scala-cli just to verify everything still works before merging any PRs to update libraries.
Anyway, I will close as stale.
@armanbilge it's a good idea to add a small example toolkit app build to CI, I'll try to do this, meanwhile we're waiting for sttp to get on sn 0.5
This is due to https://github.com/VirtusLab/scala-cli/issues/2426.