Anton Sviridov

I'd stick with `main` name tbh, to match as close as possible the naming on the Scala 3 side. Supports the argument of "hey, just add `IOApp.` to the annotation...

> oh wait you condemn that top-level cats-effect (+std) import is the only way to live. After thinking long and hard, I think I like `IO.main` the best.

Things that tripped me over personally: 1. `%%%` (so at least 1 dependency in the build definition with a comment would help a lot) 2. Testing (seeing https://github.com/scala-js/scala-js-env-jsdom-nodejs and then...

Ah yeah, wanted to add another one: - An example of accessing a JavaScript native function/class (through a facade) With dependency being kept up-to-date by scala steward, if access pattern...

Theoretically Metals _can_ fix this. ```conf version = "3.4.0" runner.dialect = scala3 rewrite.scala3.insertEndMarkerMinLines = 10 rewrite.scala3.removeOptionalBraces = true rewrite.scala3.convertToNewSyntax = true fileOverride { "glob:**.sbt" { runner.dialect = scala212source3 } "glob:**/project/**.*"...

To clarify - if Metals already takes it upon itself to update scalafmt config when it detects different build targets having different dialects, it can sure recommend to add overrides...

Which prompted me to look at the current status: https://github.com/oracle/graal/issues/2666#issuecomment-1010183689 Which is all good news, and especially with them hooking up M1 to the infra, to produce images for 17...

And even after that it might be problematic until GHA add a M1 runner - otherwise there's no way to produce M1 native binaries on CI.

Glad I remembered this issue :) I can reproduce it without Scalacheck, in the following build: https://github.com/keynmol/jobby/actions/runs/3209965828/jobs/5247080202 What's fascinating is that in the same build I have tests that use...

Here's the full sequence of debug logging: ``` 2022.10.08 11:06:58:866 io-compute-9 INFO 🐳 [testcontainers/ryuk:0.3.3] Creating container for image: testcontainers/ryuk:0.3.3 Container testcontainers/ryuk:0.3.3 is starting: 74e76644f679a4ede92aff2a563bbdfd28dcbf9add0ead2ea393999114d92130 Container testcontainers/ryuk:0.3.3 started in PT0.536578S [info]...