Bug #105022 for Type-Tiny: coercions fail to be executed on uncompiled type checks

Sat Jun 06 14:05:28 2015 MITHALDU [...] cpan.org - Ticket created

Subject:

coercions fail to be executed on uncompiled type checks

I have a test script for this here: https://gist.github.com/wchristian/14e15cdc061c5d080115

Sun Jun 07 08:32:39 2015 haarg [...] haarg.org - Correspondence added

The "uncompiled type check" is using the codification overload on a Type::Tiny object, which is documented to use $type->assert_return. The "compiled type check" is a compiled parameter validation sub, which can validates arguments against a signature. It is documented to apply coercions. I don't see a bug here.

Sun Jun 07 08:32:39 2015 The RT System itself - Status changed from 'new' to 'open'

Sun Jun 07 09:04:29 2015 MITHALDU [...] cpan.org - Correspondence added

Show quoted text

> The "uncompiled type check" is using the codification overload on a > Type::Tiny object, which is documented to use $type->assert_return.

There's two bugs to that then, as far as documentation goes: 1. The "Validation-and-coercion" section lacks an explicit mention of the overload behavior. 2. The "Validation-and-coercion" section lacks an explicit mention of the fact that no validation method will coerce, except for the mentioned actual coerce methods. https://metacpan.org/pod/Type::Tiny#Validation-and-coercion

Tue Jan 31 23:05:10 2017 perl [...] toby.ink - Status changed from 'open' to 'rejected'