1 -------------------------------------------------------------------------------
3 -------------------------------------------------------------------------------
7 Need to figure out the details of composite roles
11 Add support for doing it with Classes which do not have
12 a type constraint yet created
18 - inherited slot specs
20 'does' can be added to,.. but not changed
21 (need type unions for this)
25 a proxied attribute is an attribute
26 which looks like an attribute,
27 talks like an attribute, smells
28 like an attribute,.. but if you
29 look behind the curtain,.. its
30 over there.. in that other object
32 (... probably be a custom metaclass)
34 - compile time extends
36 [00:39] sri but maybe a better syntax for compile time extends
37 [00:39] stevan I have been pondering that actually
38 [00:39] sri use Moose extends => Foo::Bar
39 [00:40] stevan I think now that we have the Sub::Exporter stuff
40 in, that kinda thing should be pretty easy
42 nothingmuch notes that all the constructs should be supported in the entirety of the use clause:
50 and that if this usage style is used nothing is exported to the namespace.
52 - default should dclone()
54 - subtype $anon_subtype => where { ... }
56 [22:56] stevan sub mst_doesnt_like_to_type { (shift)->meta->attr->type_contstraint }
59 [22:57] stevan are you wanting to reuse it or something?
60 [22:57] stevan my $subtype = subtype 'Something' => where { ... };
61 [22:58] stevan then you can do isa => $subtype
62 [22:58] mst but I can't subtype it again
63 [22:59] stevan mst: ahhh...
64 [22:59] mst well, I can. but it suddenly gets very "long way round" ish
65 [23:00] stevan my $constraint = Moose::Meta::TypeConstraint->new(
66 [23:00] stevan name => $name || '__ANON__',
67 [23:00] stevan parent => $parent,
68 [23:00] stevan constraint => $check,
69 [23:00] stevan message => $message,
71 [23:00] stevan yeah thats kinda the long way
72 [23:00] stevan mst: what would you like it to be?
73 [23:00] mst $parent = find_type_constraint($parent) if defined $parent;
74 [23:00] mst if $parent is already a type constraint
75 [23:00] mst skip that bit
77 [23:00] mst should be all you need to change
79 [23:01] stevan so you can then say
80 [23:01] stevan subtype $anon => where { ... };
86 [23:37] mst more seriously, I'd still like a "method" keyword or something
87 [23:37] mst method 'foo' => sub { ... };
88 [23:38] stevan what would it do more than sub foo { ... }?
89 [23:39] stevan I would like multimethods actually
90 [23:39] mst almost exactly nothing, to begin with
91 [23:39] stevan but thats just cause I love CLOS and am reading a book on Dylan now
92 [23:40] stevan keyword squating :)
93 [23:40] mst but if we need to hook stuff later it's bloody handy to already have people writing it that way
96 [23:49] mst oh, also: method 'has' => sub { ... } could squelch the redefine warning
100 [17:00] stevan I am reading the new Fortress Spec
101 [17:00] stevan http://research.sun.com/projects/plrg/fortress0903.pdf
102 [17:00] stevan they have traits too
103 [17:01] stevan and they have one cool feature which we might want to steal
104 [17:01] stevan traits can "exclude" other traits
105 [17:01] stevan which means they cannot be combined with other classes/roles which does() that trait
106 [17:01] stevan the example they give is
107 [17:01] stevan trait OrganicMolecule extends Molecule
108 [17:01] stevan excludes { InorganicMolecule }
110 [17:01] stevan trait InorganicMolecule extends Molecule
112 [17:01] stevan this creates a set of mutually exclusive traits
113 [17:02] stevan so that this:
114 [17:02] stevan trait ScienceGoo extends { OrganicMolecule, InorganicMolocule } end
115 [17:02] stevan would fail
116 [17:02] stevan because OrganicMolecule, InorganicMolocule can never be used together
117 [17:03] stevan I am thinking this is quite sane
119 -------------------------------------------------------------------------------
121 -------------------------------------------------------------------------------
123 - Moose "strict" mode
125 use Moose 'strict'; This would allow us to have all sort of expensive tests
126 which can be turned off in prod.
128 - Moose::Philosophy.pod
130 To explain Moose from a very high level
134 We certainly have enough meta-information to make pretty complete POD docs.