Eric K Richardson
Eric K Richardson
Late discovery is not super great because then the global instance of `NativeConfig` is empty so showing it is pretty much useless. I tried various approaches and none are as...
We do have this repo for putting the old code to help with `0.5.0` migration: https://github.com/scala-native/scala-native-java-stubs Unfortunately, as @LeeTibbert has done some of the homework, it will take some work...
The consideration here would be to use property files like a project descriptor where the library developer could add options etc. that could be picked up by the build. We...
Overall, this is very cool but I don't think the want to get into the Rust library building business. Rust libraries can either come with `extern C` ability or we...
Is this one of the issues? https://github.com/google/closure-compiler/issues/3707
Getting the difflib made into a scalameta project would be great. I asked Wojciech if it might work for our uses in Scala Native too.
@He-Pin Yes, that is what @kitbellew suggests above. The `difflib` might be able to be used by Scala Native too. Not sure the best way there - create a project...
I am not sure this can be back ported because it adds to `NativeConfig` but a similar problem was found during `scalafmt` compilation. https://github.com/scala-native/scala-native/pull/2819 I agree though that `release-fast` may...
In the change mentioned it had to do mostly with inline so maybe Scala 3 might be different there? Does the addition of the Optimizer in the NativeConfig break compatibility...
Pretty sure I have a solution for this.