Scala Native 0.5.x

[sideeffffect]

closes #504
closes #513
closes #493

blocked on

• Scala Native 0.5.x scala-java-locales#491

blocked on

• Update versions #509

[sideeffffect]

Any idea why Scala Native tests are always failing with this? @cquiroz @WojciechMazur

[error] Test runner interrupted by fatal signal 11
[warn] Force close java.lang.RuntimeException: Process /home/runner/work/scala-java-time/scala-java-time/tests/native/target/scala-2.12/tests-test finished with non-zero value 139 (0x8b)

I'm getting a bit desperate here...

[cquiroz]

Can't say much, I haven't use native before and since jvm and js run I'd think it is more on the native side.
does signal 11 mean it was interrupted by the github runner?

[WojciechMazur]

Looks like an issue on SN side, it's basically a segmentation fault. I'll try to minimize and fix it asap

[MateuszKubuszok]

Cats had the same error typelevel/cats#4585 (review). I am not sure what they did to make it go away

[WojciechMazur]

A quick update on the segmentation faults:
It was crashing in the Month.range(TemporalField): ValueRange methods when field was null. For some reason there is no null check before field.rangeRefinedBy(this) call to ensure we can call the method on given object - because of that it leads to referencing invalid memory address. Seems like most of range methods are having these kind of issues. I'll try to fix it over the weekend and publish fix in 0.5.3

[WojciechMazur]

The regression introduced in 0.5.x was fixed, we'd make a release soon - there is 1 more issue reported by the os-lib we'd like to ship as well. scala-native/scala-native#3939

[WojciechMazur]

0.5.3 with the fix has been released

[plokhotnyuk]

Shouldn't it be different for Scala 3?

(CrossVersion.partialVersion(scalaVersion.value) match {
    case Some((2, _)) => "-P:scalanative:genStaticForwardersForNonTopLevelObjects"
    case _ => "-scalanative-genStaticForwardersForNonTopLevelObjects"
  })

[sideeffffect]

Nope, that doesn't work. Has to be like it is currently in the PR. The tests being green are the proof :)

[WojciechMazur]

'-P' stands for prefix for compiler settings. In case of Scala.js the compiler plugin setting in Scala 2 was elevated to standalone setting in Scala 3 after Scala.js backend become a part of compiler.
Scala Native is not going to become part of compiler at least until 1.0

[sideeffffect]

@cquiroz we can merge 🎉

[cquiroz]

Thanks a lot for getting this through

[sideeffffect]

Thanks for merging! Could you please make a release @cquiroz ? 🙏