Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up0.18 should keep Task.fromResult #760
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
process-bot
Nov 25, 2016
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Nov 25, 2016
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This is a discussion to be had on the mailing list. |
jvoigtlaender
closed this
Nov 25, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
benpence commentedNov 25, 2016
I think this is a pretty useful function that @evancz got rid of in 9a1dec5 for 0.18. It's not particularly hard for me to implement, which is why I advocate for keeping it, since I expect most developers will write their own and now we've added a pinch more maintenance/bug surface for everyone.
Is there any discussion on similar topics? I'm generally pro- functions & "point free notation" over pattern matching in cases like this, but can be persuaded.