Replies: 2 comments 1 reply
|
I just came the conclusion that I was getting wrong that the union type does not have to implement |
|
@mknet Everything should work without ever needing any part of the old-style capabilities. See, for example, the counter example's The only reason that API is still around is to give older apps a chance to upgrade in their own time. Removing the associated type and third argument to We will remove every trace of the old capabilities in the future, probably a few months from now, but haven't made any final decisions yet. |
Uh oh!
There was an error while loading. Please reload this page.
At the moment, the state of the effects handling is to me in a confusing state. On one hand the docs tell me not to deriving
Effectbut to use theeffectmacro. But then I have to implementWithContextmanually if a want to invokeCore::new().If I look in the in the HelloWorld page I see the example with just
()for the associated typeCapabilitieswhich doesn't work either in case ofCore::new()usage.Am I missing something or are we in a rather difficult state of the migration from Capabilities to Managed Effects?
I'd love to help by extending the docs or examples. But before I start I just want to sync with you guys about your thoughts and ideas how I could help.
Thanks and looking forward to push crux forward.
All reactions