First the question is are Roles and Types are Symmetric. In Moose they are
not, effectively Roles are a subset of Types in Moose. This means that just because
an attribute has a Type, and a value that satisfies that Type is stored, that
does not automatically mean that an attribute’s value does a Role equivalent
to that Type. There may not be a Role that is equivalent to that type.
Second, and it took me a second to notice this, but he’s checking the
Attribute MetaObject’s does(). The Type is a property of the value stored in
the attribute, not necessarily a property of the attribute itself. So even
if the first were resolved such that a Type automatically implied a Role on
the value, this check wouldn’t be the proper one for it.
Third, if the poster is in fact looking to test a property of the
MetaObject, and if we all agree that the best way to test/implement this is
via a Role on the MetaObject, I’m not sure calling that trait after the Type
name is the most intelligent design choice. It would lead to a collision with
the way Moose’s implicit type auto-vivification happens.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
