http4s - migrate from Blaze to Ember #4185
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ivan-klass
force-pushed
the
http4s-migrate-to-ember
branch
from
16a531e to
cd1ce53
Compare
ivan-klass
force-pushed
the
http4s-migrate-to-ember
branch
2 times, most recently
from
088bbfa to
6aa2b66
Compare
ivan-klass
force-pushed
the
http4s-migrate-to-ember
branch
from
6aa2b66 to
f0b3c83
Compare
ivan-klass
force-pushed
the
http4s-migrate-to-ember
branch
from
f0b3c83 to
57c2fa6
Compare
|
Oh nice, I was worried you abandoned the PR ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ember seems to be more modern and especially better supported in terms of cross-platform builds