The advice to use unsafeCoerce strikes me as a bit harsh. It's also a bit dangerous, because someone could accidentally coerce the value to an unrelated type. I'd much rather see a Refined.Unsafe or Refined.Internal module exporting the actual constructor, and perhaps also a reallyUnsafeRefine function to get the point across.
chessai
commented
6 years ago
The advice to use
unsafeCoercestrikes me as a bit harsh. It's also a bit dangerous, because someone could accidentally coerce the value to an unrelated type. I'd much rather see aRefined.UnsafeorRefined.Internalmodule exporting the actual constructor, and perhaps also areallyUnsafeRefinefunction to get the point across.