translatenix

I think everything works as expected here. (`NonEmptyTest-Inv.pkl` isn’t the inverse test.) This should work: ``` examples { ["basic-test"] { test.catch(() -> confUnderTest.values) // or: confUnderTest.output.value } } ``` Here...

> How much perf do we gain from targeting skylake? Can you enable the native CLI builds to CI so we can compare it to the default architecture? Or, if...

> Until then, the best we can do is run benchmarks locally then compare But what benchmarks do you run? `./gradlew pkl-core:testLinuxExecutableAmd64` doesn’t strike me as a meaningful benchmark.

> Here's a quick benchmark that might be a good starting point for comparison. On my laptop, the variance of this benchmark is too high to draw any conclusions about`-march`...

> The one remaining request is to undo the change to --add-opens here. I’m still working on that. I’m not convinced that --add-opens is required. After all, it isn’t required...

Ready to review from my side. See commit messages for details. The "Improve BinaryEvaluatorSnippetTests(Engine)" refactoring isn't essential because I ultimately decided to add `NativeServerTest` instead of `NativeBinaryEvaluatorSnippetTests`. But I think...

Could someone take a look at this? It’s a significant improvement. Once I found https://www.graalvm.org/latest/reference-manual/native-image/dynamic-features/CertificateManagement/#build-time-options, everything fell in place.

To recap the current behavior: * `pkl eval bird.pkl --ca-certificates not/a/valid/path.pem` fails if and when an HTTPS request is made. * If `--ca-certificates` is not specified and `~/.pkl/cacerts` does not...

We discussed before that being lazy means that SSL initialization errors are deferred. The conclusion was that being lazy is in the Pkl spirit. Lazy SSL initialization is why 0.26...

> I don't think this is needed anymore, now that we don't use classpath resources for embedding the cert files. Removed.