You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ManickaP
added
blocking
Marks issues that we want to fast track in order to unblock other important work
api-ready-for-review
API is ready for review, it is NOT ready for implementation
and removed
api-suggestion
Early API idea and discussion, it is NOT ready for implementation
untriaged
New issue has not been triaged by the area owner
labels
Jun 13, 2024
There were questions as to why the WritesClosed property needs to still exist, but there is a legitimate scenario.
namespace System.Net.Quic;
// Existing class.
public class QuicStream : Stream
{
- public void CompleteWrites();+ public ValueTask CompleteWritesAsync();
}
bartonjs
added
api-approved
API was approved in API review, it can be implemented
and removed
blocking
Marks issues that we want to fast track in order to unblock other important work
api-ready-for-review
API is ready for review, it is NOT ready for implementation
labels
Jun 13, 2024
Background and motivation
System.Net.Quic is still in Preview, before we un-preview it, we'd like to change this method to an async one.
https://learn.microsoft.com/en-us/dotnet/api/system.net.quic.quicstream.completewrites?view=net-8.0
API Proposal
API Usage
Alternative Designs
Keeping it not-async and use existing
Task WritesClosed
property.Risks
No response
The text was updated successfully, but these errors were encountered: