Tobias Roeser

I identified it as sometimes limiting in the past. Esp. when we added new things to the context like `jobs` or `workspace` or lately `fork` to the context. It typically...

IIRC, the `==>` is defined in `utest` and stands for an equals assertion. Maybe, we could make the documentation executable and run it in CI?

Yeah. Scala.js support would be great. We gladly accept pull requests adding it.

> > Yeah. Scala.js support would be great. We gladly accept pull requests adding it. > > Is there a willingness to accept multiple PRs for this effort? Of course....

> looks like it needs a Scala Native version bump Yeah, that's the reason why we're still on `2.13.10`. We want to avoid to drop support for some platforms (like...

```console > MILL_VERSION=0.12.14 mill inspect mill.runner.MillBuild/levelCount [build.sc-61/65] compile [build.sc-61] [info] compiling 1 Scala source to /tmp/mill-2/out/mill-build/compile.dest/classes ... [build.sc-61] [info] done compiling [1/1] inspect mill.runner.MillBuild.levelCount(MillBuild.scala:13) Count of the nested build-levels, the...

Also, shouldn't we in `withTempFile` and `withTempDir` provide the same set of options as we do in the `apply` methods?

> Re supporting scala versions - does mill have standard src dirs like sbt's `src/main/scala-2.13` and `src/main/scala-3` etc? Do you have an idea on how to handle that best for...

> > We can further adapt that to our needs. > > You're much more familiar with mill than I am - can you please setup the build for a...

@mpollmeier Thanks for your analysis. Yeah, the test suite seems flaky. Sometimes it's hard to test filesystem stuff on OSes you don't have, and especially filesystems tend to behave strange/differently...