You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a compiler crash when opaque types are used with kyo-direct. It can be worked around by providing a type bound to the opaque type, which is why composite effects like Async work ok. Both Queue and Channel are opaque types and don't have a type bound. I'm not sure what we could put as the bound since we don't want to expose the APIs as their Unsafe counterparts. We might need a new wrapping class/allocation for them. More context: https://github.com/getkyo/kyo/pull/985/files#r1907969353
The text was updated successfully, but these errors were encountered:
@rssh in case you have some time to have a look. I imagine it could be due to Kyo's wrapper on top of dotty-cps-async but we can't use opaque types without bounds with the direct syntax because of compiler crashes. To reproduce, you only need the kyo-core and kyo-direct modules and then try to use Queue or Channel with the direct syntax.
There's a compiler crash when opaque types are used with
kyo-direct
. It can be worked around by providing a type bound to the opaque type, which is why composite effects likeAsync
work ok. BothQueue
andChannel
are opaque types and don't have a type bound. I'm not sure what we could put as the bound since we don't want to expose the APIs as theirUnsafe
counterparts. We might need a new wrapping class/allocation for them. More context: https://github.com/getkyo/kyo/pull/985/files#r1907969353The text was updated successfully, but these errors were encountered: