Lorenzo Gabriele

> @lolgab It's failing on `-Xms1024m`. Any idea how this parameter is supposed to be specified for Scala Native? I'm not aware of any Scala Native specific problem.

Since the API is very small you could also distribute the library as a static library so people can statically link it in their programs.

My Scala Native benchmark using `libunit` [works](https://www.techempower.com/benchmarks/#section=test&runid=0f03793d-ac4c-4869-b1fa-51fcef26d48f&test=plaintext&hw=cl&p=zik0zj-zik0zj-zik0zj-zik0zj-8vmzun) using NGINX Unit `1.29.1`.

The problem is not related to throwing exceptions (implemented by throwing an exception using C++ code). You can reproduce the same behavior just by printing a stacktrace which is written...

I opened an issue in the llvm project since I could reproduce the missing procedure name also using plain C: https://github.com/llvm/llvm-project/issues/60492

I'm going through open PRs and re-reading old comments. > I can safely detect Scala.js and Scala Native modules, but I can't detect pure Scala modules (targeting the JVM). Obviously,...

I'm having second thoughts as well about this change. What I would do instead is to standardize use: ```scala // for java deps ivy"groupId:artifactId:version" // for scala deps ivy"groupId::artifactId::version" ```...

> @lefou don't mill plugins use `group::mill-foo:$MILL_VERSION`? I don't recall seeing the double colon syntax used in the context of mill plugins before What you describe are the contrib plugins...

Two things that might influence the discussion: - Sbt 2.0 is [designing a solution for this same problem now](https://eed3si9n.com/sbt-2.0-ideas). It's worth checking what they are doing, even though they have...

Why do we need to a add a new type of `Dep`? Why can't `Dep` itself be what `BoundDep` is?