Bug #102638 for Type-Tiny: "Default" type constraint for using with Dict and Tuple

Sun Mar 08 09:14:04 2015 ZDM [...] cpan.org - Ticket created

Subject:

"Default" type constraint for using with Dict and Tuple

Hi. Maybe it will be useful to add "Default" constraint. Dict [ aaa => Default [Num, 10], bbb => Default [20], ] It should check if key exists, and if exists - validate value type, if type constraint present. If key not exists - create key with default value. And the same for Tuple. I can prepare patch request, if you do not mind.

Mon Feb 06 16:33:39 2017 perl [...] toby.ink - Correspondence added

Type constraints don't (and shouldn't) alter the values they check. Could possibly be done with type coercions though. I'd *consider* accepting an implementation of this. The whole point of Type::Library though, is that you can publish your own libraries of constraints and coercions — they don't need to be built into Type::Tiny.

Mon Feb 06 16:33:39 2017 The RT System itself - Status changed from 'new' to 'open'

Mon Feb 06 16:33:39 2017 perl [...] toby.ink - Status changed from 'open' to 'rejected'

Mon Feb 06 17:09:51 2017 dzagashev [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #102638] "Default" type constraint for using with Dict and Tuple
Date:	Tue, 7 Feb 2017 00:09:26 +0200
To:	bug-Type-Tiny [...] rt.cpan.org
From:	"dzagashev [...] gmail.com" <dzagashev [...] gmail.com>

yes, I am agree. On 06.02.2017 23:33, Toby Inkster via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=102638 > > > Type constraints don't (and shouldn't) alter the values they check. Could possibly be done with type coercions though. > > I'd *consider* accepting an implementation of this. The whole point of Type::Library though, is that you can publish your own libraries of constraints and coercions — they don't need to be built into Type::Tiny. >