Optimize ServerInboundHandler#writeResponse
#3057
Merged
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
|
CI failure is "expected". It should be fixed by #3056 |
|
@kyri-petrou Long overdue cleanup! ❤️ |
jdegoes
approved these changes
Aug 27, 2024
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.
Currently, the error handling in
ServerInboundHandler#writeResponserequires 3foldCauseZIOs and 3-4flatMaps as well as a couple ofsucceed.This PR rewrites this logic in order to:
ZIO.attempt/ZIO.suspend)foldCauseZIOinstead ofsandbox+catchAllThis results in just 1
foldCauseZIOin the happy path (success &attemptFastWriteis successful). And as a plus, the code is also much cleaner and easier to follow