What's the reasoning for not putting Task
in the standard library? It seems like it operates in a similar manner as Result
does, which is in there. Would be helpful if all platforms used the same API for Task
s and switching platforms wouldn't require learning/understanding a new API? Or is there an expectation that Task
s should work differently on different platforms?
Tasks will be added to std lib. Here is the design proposal that is accepted but not yet implemented.
I think the main issue preventing it rn is the implementation of effect interpreters which has been challenging.
Note that I think the Stored
ability is no longer planned to be implemented, but that is just what I've picked up from the discussion here, it's still in the original proposal.
Thanks for that! I'll have to give that a read
Last updated: Jul 06 2025 at 12:14 UTC