Michael Pollmeier

Re your other thoughts with "TempPaths and still provide the deleteOnExit option" etc. - I don't have a strong opinion either way, but would prefer to keep it simple. Automagically...

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 this...

> 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 few scala versions...

Thank you, that worked! I tried to split up the functionality from `object temp` into `src` (for the universally working parts), `src-2.13+` (for whatever relies on `Using`) and `src-2.12-` (with...

About those CI failures - I wasn't convinced first, but they're actually legit... For some reason, calling `os.remove.all(this)`: ```scala class TempPath private[os] (wrapped: java.nio.file.Path) extends Path(wrapped) with AutoCloseable { override...

Sorry about the silence! I thought it was ok because the attribution (copyright, license) are in the file, but yes I agree, it's better to have less code either way....

Hmm, we seem to have some flakey tests in there, parts of `test.os.ExampleTests` fail from time to time. This doesn't seem related to this PR, the same happens with `main`...

I'm locally running `./mill -i -k __.test` on the `main` branch in a loop and the results are very flakey: ``` grep target build-output.txt | grep ' failed$' 1 targets...

Since this flakeyness is happening on `main`, I was curious and tested past tags as well. Even if I go back to `0.4.0` it's flakey - at least for me...

> Good idea, @mpollmeier could you give this a look? I recall some basic metrics captured in ODB but not sure if it's done at this level to include memory...