Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move mWriteResponseBuilder in WriteHandler to stack #14943

Closed
erjiaqing opened this issue Feb 9, 2022 · 1 comment · Fixed by #15068
Closed

Move mWriteResponseBuilder in WriteHandler to stack #14943

erjiaqing opened this issue Feb 9, 2022 · 1 comment · Fixed by #15068
Assignees

Comments

@erjiaqing
Copy link
Contributor

As a followup (please do not try to address this in this PR): is there a reason mMessageWriter and mWriteResponseBuilder need to be persistent members of this object? Shouldn't they just have stack lifetime here?

Originally posted by @bzbarsky-apple in #13641 (comment)

@bzbarsky-apple
Copy link
Contributor

OK, mWriteResponseBuilder is used in a bunch of methods called from various places outside this class, so having it be a member makes some sense. But mMessageWriter I am pretty sure we can move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants