WWWWWW

Current Directory: /usr/share/doc/perl-Moose/doc
Viewing File: /usr/share/doc/perl-Moose/doc/moosex-compile
MooseX-Compile, wherein Yuval explains how MooseX::Compile is supposed to work and what needs doing.

TODO: PLEASE EDIT ME

11 <obra> hiya
12 <nothingmuch> hola
13 <obra> so, my empty mail was an attempted abort
13 <obra> but was going to be "MX::Compile doesn't depend on MX::Compile::CLI. should it?"
13 <nothingmuch> ah, ok =)
13 <obra> but i'm without my laptop, so i couldn't actually check my assumption
14 <nothingmuch> no, because MX::Compile::CLI is "just a a frontend" and at the time the dependencies were a little sketchy
14 <nothingmuch> they've since matured, so maybe it should dep
21  * obra nods
21 <obra> I was on a plane and was trying to see if MX::Compile was at the point where I could try trivial tests
22 <nothingmuch> ah
22 <nothingmuch> so the answer is definitely maybe ;-)
22 <nothingmuch> i haven't been able to make time for it in the past week
23 <nothingmuch> if you guys hand me small, targetted test cases (just commit to it) of code that passes under plain Moose and should pass with MX::Compile i can probably do that stuff pretty quickly
23 <nothingmuch> but the biggest barrier MXC has right now is testing, in order for it to progress towards something production worthy it basically needs to pass the Moose test suite
23 <nothingmuch> except without the Moose test suite's assumptions
23 <nothingmuch> about state and module loading, and all that
24 <nothingmuch> and doing that is a much more daunting prospect than hacking on MXC itself
24 <obra> understood. the problem is that I still don't have a good sense of how to get it going, even manually
24 <nothingmuch> ah
24 <obra> none of the test files seem to show off what I need
24 <nothingmuch> i can walk you through thjat
25 <nothingmuch> the assumptions of the system are:
25 <nothingmuch> the class you are compiling is in its own .pm using standard moose sugar
25 <nothingmuch> there is one package in that file
26 <nothingmuch> the compiler object takes the metaclass and the .pm file as args
26 <nothingmuch> it serializes the metaclass to a .mopc file, and the generated code into a .pmc
26 <nothingmuch> the .pmc contains the original .pm verbatim
26 <nothingmuch> except that all the moose sugar does nothing
27 <nothingmuch> meta is overriden to lazy load .mopc
27 <nothingmuch> and the class is supposed to be usable without loading Moose at all
27 <obra> what is the point of containing the original pm verbatim?
27 <nothingmuch> the user code
28 <nothingmuch> could open and slurp and eval
28 <nothingmuch> but this is a little more flexible
28 <nothingmuch> basically any subroutines the user has written, global/lexical variable initialization, loading of assorted modules etc all must work
28 <obra> are you using the flexibility?
28 <obra> (open, slurp, eval sounds suspiciously like "do")
29 <nothingmuch> can't use do/require/etc because it will go to the .pmc
29 <nothingmuch> instead of the .pm
29 <nothingmuch> the flexibility is helpful because you get a lexical set if the code is compiled
29 <nothingmuch> for when you need to do trickery
29 <nothingmuch> see Moose/Object.pm
29 <obra> I didn't think 'do' had that logic. but ok :)
30 <obra> anyway
30 <obra> do go on
30 <nothingmuch> now that we have Devel::Declare that might prove even simpler
30 <nothingmuch> simply replacing has() etc to export the subs inline
30 <nothingmuch> and write the resulting buffers to a .pmc
30 <nothingmuch> but that's for Later™
30 <obra> The fact that the TM shows up in my terminal scare me
30 <obra> but only a bit less than that you typed it ;)
30 <nothingmuch> utf8++
31 <obra> ubuntu++
31 <nothingmuch> most linuxes seem to get that refreshingly right
31 <nothingmuch> so, erm
31 <obra> yeah. it's pleasant.
31 <nothingmuch> mxcompile
31 <obra> anyway
31 <nothingmuch> that is a nice frontend to the compiler object
31 <obra> I guess "what do I need to do to try MX::Compile for prophet+sd?"
31 <nothingmuch> it can recurse through a directory of modules, or take a list of classes
31 <nothingmuch> for starters, role support
31 <nothingmuch> i know how to do it
31 <nothingmuch> but haven't yet
32 <nothingmuch> type constraint support is very primitive
32 <obra> is that essentially the same code sartak needs to write to give Mouse roles?
32 <nothingmuch> i don't know what that is but doesn't sound likely
32 <nothingmuch> in MXC moose has already done the role composition
32 <nothingmuch> i just need to figure where the data came from, load that file and realias the subs
33 <nothingmuch> (at bootstrap time)
33 <nothingmuch> no role composition per se
33 <nothingmuch> it's nice to make clear that MXC has two "levels" of awesome
33 <nothingmuch> so you can figure out what you can hope to achieve
34 <nothingmuch> 100% compiled everything means you don't load Moose or Class::MOP
34 <nothingmuch> until you need runtime reflection
34 <nothingmuch> no codegen at compile time
34 <nothingmuch> it should load as fast as hand written code
34 <nothingmuch> i've had it beating Object::Tiny in some benchmarks =)
35 <obra> oo
35 <nothingmuch> Moose::XS should aid in making MooseX::Compile's supported feature set easier
35 <nothingmuch> the less awesome level of awesome is just some classes
35 <nothingmuch> you don't pay for those classes' compilation (Role composition, etc)
35 <obra> (especially since for me perl -MMoose -e1 takes up 50% of "sd help"'s runtime
36 <obra> (.4s here)
36 <nothingmuch> 5.8.8/
36 <nothingmuch> ?
36 <obra> yeah
36 <obra> "that's what's in the wild"
36 <nothingmuch> i'm just curious if it makes a dfif
36  * obra nods
36 <obra> I don't have my macbook right now or I'd test
36 <nothingmuch> trunk moose loads slower
36 <obra> how much slower?
36 <nothingmuch> but 5.10 loads faster
36 <nothingmuch> negligiably
36 <nothingmuch> i think like 10%
36 <obra> this was trunk moose as of friday
36 <nothingmuch> but we can fix that
36 <nothingmuch> ah
36 <obra> my tests aren't scientific.
36 <nothingmuch> trunk moose as of you sending me nytprofs
37 <nothingmuch> actually that's CPAN moose now
37 <obra> 0.35 - 0.45
37 <nothingmuch> ouch
37 <nothingmuch> well, part of the problem is that it loads *EVERYTHING*
37 <nothingmuch> every type of meta method class, meta type constraint, the role system, etc
37 <nothingmuch> for a big app these probably will get loaded
38 <nothingmuch> but for a small app, especially if you load the various sub modules only as needed, you shouldn't pay for these
38 <nothingmuch> that's a trivial fix that perigrin started working on
38 <obra> yeah. I played with his branch and saw no change as of last night
39 <obra> so yeah, we're using roles. if roles aren't ready yet, I won't get far at all.
39 <obra> (Also, I do really appreciate all the work you're doing. That I'm not paying for, even ;)
39 <obra> Thank you.
39 <nothingmuch> i will try shaving Moose's own load time with a profile based approach
39 <obra> It's SO MUCH better than it was
39 <nothingmuch> well, everybody wins =)
39 <nothingmuch> a. you're a friend
40 <nothingmuch> b. part of my job is making Moose work well
40 <nothingmuch> c. your using Moose helps moose directly and indirectly
40 <nothingmuch> d. I LIKE TACOS
40 <nothingmuch> erm, i mean sushi
40 <nothingmuch> so no worries on that
41 <nothingmuch> so, long term goals:
41 <nothingmuch> App::SD etc has all the meta calculations already cached in .mopc and .pmc
41 <nothingmuch> moose is not loaded
41 <nothingmuch> all generated code is cached
41 <nothingmuch> at worst Moose::XS is loaded to install subs with newXS
41 <obra> that would be really cool
41 <nothingmuch> depending on which actually fairs better
42 <nothingmuch> that goal is realistic, but involves a lot of work
42 <nothingmuch> more realistic short term goals:
42 <obra> I started playing with try to dump the symbol table, etc
42 <nothingmuch> MooseX::Compile partly speeding up SD
42 <nothingmuch> we can incrementally improve on that
42 <obra> and found that DD::Streamer is a lot closer than anything has ever been, but it craps out around not being able to dump lvalue subs
43 <nothingmuch> Moose::XS replacing some code gen
43 <nothingmuch> yes, the initial approach was to to try and marshall Moose classes into DDS
43 <nothingmuch> but it wasn't stable enough
43 <nothingmuch> and also there's the problem of imports
43 <nothingmuch> you must serialize the whole table at once
43 <nothingmuch> or manage an intricate web of inter dependencies
43  * obra nods
44 <nothingmuch> i sort of work around that by making all the require()/use() statements stay verbatim
44 <nothingmuch> also it doesn't handle xsubs
44 <obra> how hard would it be to get moose's codegen to write out source code instead of blowing subs into memory?
44 <nothingmuch> so there's guesswork for where ::bootstrap was called
44 <nothingmuch> i was just getting to that =
44 <nothingmuch> =)
44 <nothingmuch> pretty trivial
44 <obra> heh
44 <nothingmuch> just grunt work
44 <obra> is that a more viable approach?
44 <nothingmuch> it's one of the limiting parts of MooseX::Compile
45 <nothingmuch> if we clean up that code it will be easier to add support for more features
45 <nothingmuch> but it's not a huge hurdle since it's a very contained problem
45 <nothingmuch> it doesn't directly affect the design of MXC
45 <obra> is this stuff written down anywhere other than this buffer?
45 <nothingmuch> i don't think so
46 <obra> where should it get pasted?
46 <nothingmuch> good question =)
46 <nothingmuch> i think #moose-dev is pretty aware
46 <obra> is there a moose wiki?
46 <nothingmuch> but documenting is good for people to help out
46 <nothingmuch> no, there should be
46 <obra> yeah. but the goal is to turn it into written docs.
46 <obra> ok. for now, it should end up in MooseX-Compile/doc/design
46 <nothingmuch> sounds good
46 <obra> . o O { Thank god I don't have a moose commit bit }
47 <nothingmuch> though most of this affects moose itself though
47  * obra nods
47 <obra> Moose/doc/moosex-compile, then
F1l3 Manager
