perf: keep using lightweight Response object when retrieving headers, status and ok for feat-get-response-state-v24 branch#3
Closed
usualoma wants to merge 4 commits intofeat-get-response-state-v24from
Conversation
usualoma
force-pushed
the
feat-more-use-respose-cache
branch
from
6e4ac4d to
89b5838
Compare
usualoma
changed the title
headers, status and okheaders, status and ok for feat-get-response-state-v24 branch
This was referenced May 17, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Until now, when accessing a property, a (heavy) original Response object was created immediately, but in this PR, for frequently accessed properties, a (light) cache will continue to be used.