With these removed, WaitForDataOrEof and the condition variable are also removed.
This was merged as part of #30205, in advance of #26812, which never landed.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | jpk68, willcl-ark, sedited |
If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
With these removed, WaitForDataOrEof and
the condition variable are also removed.
ACK e172eb69df92b5ef9cd5f4234de28430c1f7b7b8
utACK e172eb69df92b5ef9cd5f4234de28430c1f7b7b8
Nice cleanup that also removes (some tiny) unnecessary notification overhead.
Removing the unused blockign read path lets us drop the condition variable and its notifications from writes and EOF handling.
Using LOCK also makes it clearer that GetBytes() takes the mutex without waiting for data.
Reproduced ACK e172eb69df92b5ef9cd5f4234de28430c1f7b7b8
I think if we ever want this back again in the tests, this seems straight forward enough to add back.