Why default to a no-op? about dry-types HOT 3 CLOSED

it defines a float type, treat it like something for type annotations, it's going to be a base for more complex types, ie a constrained float that must meet specific requirements.

from dry-types.

Yeah, but it's really surprising that the default behavior of the type is to not care if it's actually of that type.

from dry-types.

As I said, this is the base construct for other types, when you actually don't want to have coercions at all, for type-checking there is strict category, for coercions there is coercible category, etc. A base is needed, the readme explains it. It represents information about the type, it's not meant to be used for coercion.

Simple annotations are useful too, ie when you trust the source to always provide already coerced input, but you do want to specify information about the types.

from dry-types.