Mark Hammons

I would like to say > javac allows programmers to declare module requirements, exports inline in the sourcetree ("module-info.java" files). What should we do? is of great importance to me....

@LeeTibbert I can start work again on this soon (I'm pursuing development in scala native once again), but for now I'm not available.

That's perfectly fine, please don't worry about it.

LGTM

Apparently, HIP is just a shim over nvcc/opencl libs, and not an actual library. Unfortunately that means I can't make a jnr-ffi binding to it, but if there's a hiprtc...

so as an example, I run: ``` [mhammons@localhost Dramaturge]$ ./mill _.test No mill version specified. You should provide a version via '.mill-version' file or --mill-version option. Retrieving latest mill version...

This couldn't be run before on mill 0.10.7. Scala 3.2 wasn't supported yet.

I've enabled all the compileTime/linkTime debug I had working on SBT, and this consistently happens ``` ================================================================= ==30458==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe5a27e6f8 at pc 0x55c79f233fd3 bp 0x7ffe5a27e570 sp 0x7ffe5a27e568...

> Just to isolate the issue, is it possible to use Scala 3.1.x for a repro? When yes, does it fail too and with both Mill versions? The above happens...

Regarding the lost results: ``` val res = TestModule.handleResults(doneMsg, results, Some(T.ctx())) // Hack to try and let the Scala Native subprocess finish streaming it's stdout // to the JVM. Without...