Kasey Speakman
Kasey Speakman
Ah, so this would represent an unofficial shift in the naming guidelines. At least, I would use camel case property names to have access to this feature for the use...
@cartermp I'm into it. :) We inherited most of the guidelines from C# anyway.
My alternative strategy is to create a shareable validation function for the type. And always validate it before executing logical workflows using it. That way anyone can construct a value...
My response was for anyone arriving here looking to solve the problem with what we have today. And really, you can't be as certain with a private constructor because it...
For example, Newtonsoft will happily construct a record with all null/default values. Even though this is not idiomatic F# (or even valid as declared F#), it is allowed by CLR...
CLIMutable doesn't matter (and I don't use it). Newtonsoft will find and use the record constructor of "regular record types". And in absence of values in the JSON it will...