You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've preference for testing presence with has_foo where the foo attribute has required => 0 over using a is => MayBe[] construct. I think this plays better with MooseX::GetOpts, and also seems more precise (at the cost of moving further from non-Moose Perl to more Moose Perl).
On 09/12/2016 09:06, dkj wrote:
I've preference for testing presence with |has_foo| where the |foo|
attribute has |required => 0| over using a |is => MayBe[]| construct.
I think this plays better with MooseX::GetOpts, and also seems more
precise (at the cost of moving further from non-Moose Perl to more
Moose Perl).
Following on from (but not blocking) #86
<#86>
|MayBe[] is needed when undef has to be assigned explicitly. If an
explicit assignment can be avoided, then ||it should be possible to
avoid ||MayBe[] as well and get by with has_foo, which is what I mostly
do these days.
Marina
|
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
I've preference for testing presence with
has_foo
where thefoo
attribute hasrequired => 0
over using ais => MayBe[]
construct. I think this plays better with MooseX::GetOpts, and also seems more precise (at the cost of moving further from non-Moose Perl to more Moose Perl).Following on from (but not blocking) #86
The text was updated successfully, but these errors were encountered: