Now that we have code coverage enabled there are a few places we can easily improve test coverage for.

• Get/Set all parameters for all types of objects
• Trigger the Settings updated code path by setting a registry key
• Test out multiple registration execution modes
• Test Server IP load balancing mode
• Packet drops in validating received initial token
• Trace ru

The main entry point of interest here is probably PartialDecode::new. This is a particularly important interface to audit as there are absolutely zero barriers to feeding data into it.

Instead of documenting build information in README.md and BUILD-WINDOWS.md, we should create a new .rst document so that it can be hosted along with the other docs on https://lsquic.readthedocs.io

The build chapter should cover:

• Building on Linux
• Building on Windows
• Building using Docker
• Building library only (without example programs, in order not to depend on libevent)
• Building

I've changed my local version to:

public QuicStreamContext CreateStream(ulong streamId = 1, StreamType streamType = StreamType.ClientBidirectional);

in order to keep the compatibility.