Experiment with scala native

[djspiewak]

It would be really interesting to see what we can do on this front, now that Scala Native is on 2.12. We would need Cats to publish for it, though. This is a rather large and sprawling project, tbh, and I'm not sure if there's even a definitive payoff at the end, but it will be cool to try anyway!

[djspiewak]

To note, the only async-anything support within scala-native comes via libuv and https://github.com/scala-native/scala-native-loop. We could technically do something like this, but it's an open question as to whether or not it would be worthwhile.

[benhutchison]

🙌 If you come up with any experiments, I'd love to test them out

[djspiewak]

This is definitely one of those things that will be a little interest-driven. 😃 Also if anyone wants to dive in and start playing with getting it working, the Cats Effect side of it would actually be very straightforward (for the most part, you just need to implement an ExecutionContext that works), and I would love to help out anyone interested in trying their hand at it.

[benhutchison]

So I did some investigating and concluded that integrating with Scala Native & libuv may be currently possible, but it's bleeding edge and exceeds my personal bravery level.

I think it might be prudent to wait for stabilization of:

• Native interop design changes, which are part-implemented ATM Proposal: Interop 2.0 scala-native/scala-native#897
• The libuv integration, eg the changes to migrate from 0.4.0-M2 to 0.4.0 have a lot of surface area, and that may continue as the native interop evolves

[JD557]

Would it probably make sense to just publish the kernel for scala native for now?

While it migh make sense to wait before porting cats IO, having the typeclasses available would allow:

• Library authors to still cross-publish code with CE3 to scala-native
• Application authors to plug in a simpler IO monad and use only a subset of operations (e.g. it should be simple to write an IO monad that only implements Sync and the required typeclasses).
• ZIO supposedly (I think there are some caveats) already supports scala-native 0.4.0, so maybe one could use that to run CE3 libraries in scala-native while the Cats IO is not ready

WDYT?

[benhutchison]

That makes sense to me. It opens the way for someone to have a go of implementing an IO on SN. Maintaining an IO for SN within CE is what I'd be wary of, as the underlying libuv bindings might keep changing for a while yet ..

…

On Sun., 14 Feb. 2021, 8:26 pm João Costa, ***@***.***> wrote: Would it probably make sense to just publish the kernel for scala native for now? While it migh make sense to wait before porting cats IO, having the typeclasses available would allow: - Library authors to still cross-publish code with CE3 to scala-native - Application authors to plug in a simpler IO monad and use only a subset of operations (e.g. it should be simple to write an IO monad that only implements Sync and the required typeclasses). WDYT? — You are receiving this because you commented. Reply to this email directly, view it on G itHub <#1302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAXJZDG2YF6JH466US2G33S66JKTANCNFSM4SMIE5ZQ> .

[ScalaWilliam]

Would it probably make sense to just publish the kernel for scala native for now?

While it migh make sense to wait before porting cats IO, having the typeclasses available would allow:

• Library authors to still cross-publish code with CE3 to scala-native
• Application authors to plug in a simpler IO monad and use only a subset of operations (e.g. it should be simple to write an IO monad that only implements Sync and the required typeclasses).
• ZIO supposedly (I think there are some caveats) already supports scala-native 0.4.0, so maybe one could use that to run CE3 libraries in scala-native while the Cats IO is not ready

WDYT?

Would be very welcome 👍

[vasilmkd]

I like the proposal.

[djspiewak]

I like the proposal as well. Could also conceivably do std as well as kernel. My main concern is that Scala Native currently doesn't support Scala 3, so the build matrix gets to be… very annoying. But, regardless, PRs welcome.

[armanbilge]

I got that cross-build fever 😅 #2168