Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Done:
HList
in favor of newTuple
Witness.T
in favor of native literal types &ValueOf
get("hello") { }
apply methods, thanks to the new fancy@targetName
. That API looks much user-friendlier now, seeMappable
. I had to do some repetitive work, but it's still cleaner for the users I hope.ToAsync
stuff that enabled Scala & Twitter Futures inMappable
. I don't think the HTTP library should do it anyway. If users want to use different effects in their app, they shall convert between them explicitly.TODO: