RedwoodForest

We need to compress requests/responses that may be tens or hundreds of megabytes in size. This along with #45 are preventing us from using this library instead of [this code](http://ronaldrosiernet.azurewebsites.net/blog/2013/07/16/implement_compression_in_aspnet_web_api)....

Hi, thanks for taking a look at this. That would fix the specific case where the token passed in is already cancelled (though I would use `CancellationToken.ThrowIfCancellationRequested()` instead of the...

It seems to me like it should be used anywhere ObjectDisposedException would be thrown instead of TaskCancelledException when an in-progress operation is cancelled. It seems like would apply anywhere Socket.Close()...

Thanks for the info @lextm. The issue for us here (and for the similar #159) is the type of exception thrown in cases like this when the server we're communicating...

@dotnetprofessional @danielmarbach, @FabianTrottmann We're looking forward to this one too! Thanks for all your hard work on this project.

@alexringeri-xero An alternative to your updated example is to move the null-forgiving operator to the initialization of the fields. I think this has less of an impact on test readability:...

@adamsitnik The prototype seems very promising! I'm hoping this feature makes it in at some point.

I found the old behavior much more intuitive. If nothing else maybe there could be an extension method or option to automatically map nullable structs as well? In case it's...

Based on my local testing it seems like changing the unit of measurement for these sensors from ```""``` to ```None``` fixes this issue. For example: ``` "status": ["Printer status", None,...