keynmol
commented
1 month ago The discussion about 0.5 is covered in governance discussions
The latest update was published in dev channel on discord:
@djspiewak: Arman and I discussed at length. A few takeaways:
We're going to bury the hatchet on IOLocal propagation and PollingSystem. The latter will land mostly as-is, the former will get a check: Poller => Boolean function to fast-path cancelation and otherwise land as-is. There's a lot of "nice to have" stuff in the 3.6 milestone which we keep kicking down the road due to lack of time and attention… and we're going to keep kicking that can down the road. This includes stuff like retry, metrics, fiber dumps in test frameworks, and other stuff. To be clear, this is all really nice to have stuff and we would love to have it, but it needs more attention than we can give right now.+ Before we do that, we're going to try to take a quick pass over things to see if anything is ready-ish to land unsafe.Queue will land in 3.6 We're going to release 3.6 against Scala Native 0.4. This is a big one but ultimately the decision came down to the fact that there's a ton of Native-shifting stuff in this release and we're just piling on more and more changes if we decide to take on 0.5. Cats can move ahead without us, but we really need to get 3.6 out the door first. The first Scala Native 0.5 CE release will be 3.7, and it's expected that SN 0.5 support will be the main focus of that release (thus hopefully reducing the timeline considerably). We'll start out trying to do multithreading and fall back from that position if it proves insane. Idk if there were other things we decided? I think that was it
TLDR - CE will have to wait for a bit longer, and when it comes, it will likely be multi-threaded
Now cats has been updated, I'm wondering if there are still blockers left?