Bolero calls JsonFSharpConverter(), which is a call to a constructor with a bunch of optional arguments. When we add more optional arguments to this constructor, the call becomes binary-incompatible. Adding a separate constructor with no arguments will fix this incompatibility.
Tarmil
commented
2 years ago
See: https://github.com/fsbolero/Bolero/issues/263
Bolero calls
JsonFSharpConverter(), which is a call to a constructor with a bunch of optional arguments. When we add more optional arguments to this constructor, the call becomes binary-incompatible. Adding a separate constructor with no arguments will fix this incompatibility.