Ch13

Would it be possible to provide a fallback to reflection to make this API available for any .NET language? As described in design doc performance isn't the only goal. Experience...

@normj Ah, sorry, I overlooked these implementation details. In this case reflection doesn't really make sense. And yes, I'm mostly worried about F#. Well, in worst scenario F#-community can come...

Noticed that the same code fails to compile with 7.0.202 SDK. Compiler treats `u` as `U2` and doesn't see `seq string>` when deducing: ``` Error FS0193 : Type constraint mismatch....

Is it only about F# specific issues? Otherwise I would throw in applicable Roslyn analyzers that are enabled by default. For example, - [CA2200: Rethrow to preserve stack details](https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2200) -...

Just to clarify, I meant those only as examples of analyzers that some people would want to port to F# SDK, hence they could be explored for SDK better designing....

> So the `nullable` would be a shorthand for putting in all nullness-related errors, on top of the option for specifying error codes individually. > > Do I understand it...