I’m the maintainer of FsCheck. Thanks for putting this together. I just wanted to add that:
“Similarly, other .NET languages just seem to adopt the policy that you should just use FsCheck to test your code rather than trying to port it to the current language.”
This is true, but not in the sense that you mean it: FsCheck has an idiomatic interface for C#/VB.NET (and documentation and code examples in F# and C#) so I can say with some confidence that a port to C#/VB.NET would not bring much to the table.
There are certainly other .NET languages, but so far I’ve felt they are too niche to support directly from FsCheck.
Hi,
I’m the maintainer of FsCheck. Thanks for putting this together. I just wanted to add that:
“Similarly, other .NET languages just seem to adopt the policy that you should just use FsCheck to test your code rather than trying to port it to the current language.”
This is true, but not in the sense that you mean it: FsCheck has an idiomatic interface for C#/VB.NET (and documentation and code examples in F# and C#) so I can say with some confidence that a port to C#/VB.NET would not bring much to the table.
There are certainly other .NET languages, but so far I’ve felt they are too niche to support directly from FsCheck.
Oh, nice. I hadn’t realised that at all, you’re right. That’s a really good idea. Thanks for letting me know!