Don Syme
Don Syme
> I’m just having a hard time finding why fsharp could not support this feature. @edgarfgp The kind of composition and reuse this sort of feature encourages is at odds...
@abelbraaksma Strictly speaking, that warning only applies when the new-type directed ways of getting subtyping conversions. That's because these have more potential to be troublesome under code refactorings than the...
@abelbraaksma OK, so you mean examples 2 and 3, sorry, I didn't read past example 1, my bad . Can you remove example 1 from the report? (though note I...
I believe "null" is always emitted as a unit value. To my knowledge there is not even a singleton unit value in FSharp.Core. In a way Unit should be labelled...
Marked as approved in principle!
Try using `fsiAnyCpu` - `fsi` runs 32-bit by default
A partial fix to this is here: https://github.com/fsprojects/FSharp.Data/pull/1503 An additional package needs to be referenced, or we must move to later .NET for the design time component
I guess we should interpet this as a request for a feature request for a new static parameter `StrictBooleans` to the CsvProvider so that the provider only infers a boolean...
e.g. torch.quantize_per_channel(input, scales, zero_points, axis, dtype) → Tensor and the other basic support for quantized tensors in `torch::*quant*`
Note we use combo packages in DiffSharp to give a single package to reference - the above would also simplify DiffSharp and correctly put the sanity checking for an overall...