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
As you can see in this little example, BindT returns a Task<Option> as expected.
MapT however returns Task<Option<Task>>, but I would expect Task<Option> like it does in BindT.
The difference is while BindT has an overload where it expects a Func with a Task as return value, MapT doesn't seem to be prepared for it. My suggestion would be adding a similar overload to MapT. Or do I miss something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm new here and I don't know if this was suggested or discussed already, at least I didn't find anything.
I came across following "issue":
As you can see in this little example, BindT returns a Task<Option> as expected.
MapT however returns Task<Option<Task>>, but I would expect Task<Option> like it does in BindT.
The difference is while BindT has an overload where it expects a Func with a Task as return value, MapT doesn't seem to be prepared for it. My suggestion would be adding a similar overload to MapT. Or do I miss something?
Beta Was this translation helpful? Give feedback.
All reactions