Daniel Urban

It seems something similar(?) can happen with `.withOptimize(true)`: https://github.com/durban/choam/actions/runs/17179593920/job/48740253842#step:18:480 For future reference (as github will delete the logs): ``` java.lang.NoClassDefFoundError: cats.effect.tracing.TracingConstants$ Caused by: java.lang.IllegalStateException: Failed to load module initialized by...

Still happens with 0.5.9: https://github.com/durban/choam/actions/runs/19555915926/job/55998189969#step:18:1585 The relevant part of the log, for posterity: ``` [info] Starting process '/Users/runner/work/choam/choam/data/native/target/scala-2.13/choam-data-test' on port '49319'. ScalaNative: Unrecoverable StackOverflow error in user thread, stack size...

Which branch? Possibly related: #4446.

I think it does. I've even mentioned it in the PR. (Okay, I've mentioned MutexSpec, but I think this is probably the same.) (I could reproduce #4448 locally by putting...

Somewhat related issue: #3442.

Did you take a look at #4525? What's your opinion on the question I've asked there?

Well, "amused" is one word for it :-) So it's not a _bug_ in Scala.js, as in, it behaves as documented: dereferencing `null` is undefined behavior in Scala.js (LOL, what?...

That we do check. It's this line: https://github.com/typelevel/cats-effect/blob/series/3.x/core/shared/src/main/scala/cats/effect/IO.scala#L2024 (and `fa` is null).

It's annoying, because in Scala they _are_ null safe. (The test passed before, it just failed on JS.) We'd have to do something like this (everywhere), to make it work...

(Just some context about the `null` test you've removed: I've added that on my old branch, because I've had a bug previously in my implementation, where it didn't handle correctly...