Commit | Line | Data |
8b59f8d6 |
1 | ------------------------------------------------------------------------------- |
43d599e5 |
2 | BUGS |
3 | ------------------------------------------------------------------------------- |
4 | |
5 | mst: if I do "subtype 'Foo' => as 'Bar';" I get an empty condition and it dies |
6 | |
7 | ------------------------------------------------------------------------------- |
8b59f8d6 |
8 | TODO |
9 | ------------------------------------------------------------------------------- |
10 | |
8b59f8d6 |
11 | - type unions |
12 | |
13 | Add support for doing it with Classes which do not have |
14 | a type constraint yet created |
15 | |
16 | - type intersections |
17 | |
18 | Mostly just for Roles |
19 | |
20 | - inherited slot specs |
21 | |
db1ab48d |
22 | 'does' can be added to,.. but not changed |
23 | (need type unions for this) |
8b59f8d6 |
24 | |
8b59f8d6 |
25 | - proxy attributes |
26 | |
db1ab48d |
27 | a proxied attribute is an attribute |
28 | which looks like an attribute, |
29 | talks like an attribute, smells |
30 | like an attribute,.. but if you |
31 | look behind the curtain,.. its |
32 | over there.. in that other object |
33 | |
34 | (... probably be a custom metaclass) |
8b59f8d6 |
35 | |
36 | - compile time extends |
37 | |
38 | [00:39] sri but maybe a better syntax for compile time extends |
39 | [00:39] stevan I have been pondering that actually |
40 | [00:39] sri use Moose extends => Foo::Bar |
41 | [00:40] stevan I think now that we have the Sub::Exporter stuff |
42 | in, that kinda thing should be pretty easy |
43 | |
8245db56 |
44 | nothingmuch notes that all the constructs should be supported in the entirety of the use clause: |
45 | |
46 | use Moose ( |
47 | has => foo ( |
48 | .... |
49 | ), |
50 | ); |
51 | |
52 | and that if this usage style is used nothing is exported to the namespace. |
53 | |
8b59f8d6 |
54 | - default should dclone() |
55 | |
8a157bab |
56 | - subtype $anon_subtype => where { ... } |
57 | |
58 | [22:56] stevan sub mst_doesnt_like_to_type { (shift)->meta->attr->type_contstraint } |
59 | [22:57] mst err |
60 | [22:57] stevan :P |
61 | [22:57] stevan are you wanting to reuse it or something? |
62 | [22:57] stevan my $subtype = subtype 'Something' => where { ... }; |
63 | [22:58] stevan then you can do isa => $subtype |
64 | [22:58] mst but I can't subtype it again |
65 | [22:59] stevan mst: ahhh... |
66 | [22:59] mst well, I can. but it suddenly gets very "long way round" ish |
67 | [23:00] stevan my $constraint = Moose::Meta::TypeConstraint->new( |
68 | [23:00] stevan name => $name || '__ANON__', |
69 | [23:00] stevan parent => $parent, |
70 | [23:00] stevan constraint => $check, |
71 | [23:00] stevan message => $message, |
72 | [23:00] stevan ); |
73 | [23:00] stevan yeah thats kinda the long way |
74 | [23:00] stevan mst: what would you like it to be? |
75 | [23:00] mst $parent = find_type_constraint($parent) if defined $parent; |
76 | [23:00] mst if $parent is already a type constraint |
77 | [23:00] mst skip that bit |
78 | [23:00] stevan hmm |
79 | [23:00] mst should be all you need to change |
80 | [23:00] stevan yeah |
81 | [23:01] stevan so you can then say |
82 | [23:01] stevan subtype $anon => where { ... }; |
83 | [23:01] mst right |
84 | [23:01] stevan ok |
85 | |
86 | - method keyword |
87 | |
88 | [23:37] mst more seriously, I'd still like a "method" keyword or something |
89 | [23:37] mst method 'foo' => sub { ... }; |
90 | [23:38] stevan what would it do more than sub foo { ... }? |
91 | [23:39] stevan I would like multimethods actually |
92 | [23:39] mst almost exactly nothing, to begin with |
93 | [23:39] stevan but thats just cause I love CLOS and am reading a book on Dylan now |
94 | [23:40] stevan keyword squating :) |
95 | [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:40] mst right |
97 | ... |
98 | [23:49] mst oh, also: method 'has' => sub { ... } could squelch the redefine warning |
43d599e5 |
99 | |
8b59f8d6 |
100 | ------------------------------------------------------------------------------- |
101 | TO PONDER |
102 | ------------------------------------------------------------------------------- |
103 | |
104 | - Moose "strict" mode |
105 | |
106 | use Moose 'strict'; This would allow us to have all sort of expensive tests |
107 | which can be turned off in prod. |
108 | |
109 | - Moose::Philosophy.pod |
110 | |
111 | To explain Moose from a very high level |
112 | |
687e52bb |
113 | - moosedoc |
8b59f8d6 |
114 | |
687e52bb |
115 | We certainly have enough meta-information to make pretty complete POD docs. |
8b59f8d6 |
116 | |
117 | |
8245db56 |
118 | |