> The M in Moose is for Metamodel, and if I wanted custom object behavior in
> Perl6, I would subclass it's standard metamodel and then override what needs
> changing eg STORE/FETCH.
>
> No idea how to do that, or it's feasiblity. Just have the impression that the
> point of having a
The M in Moose is for Metamodel, and if I wanted custom object behavior in
Perl6, I would subclass it's standard metamodel and then override what
needs changing eg STORE/FETCH.
No idea how to do that, or it's feasiblity. Just have the impression that
the point of having a metamodel is for this
Lets take the question of 'do I really need AttrX::Mooish' out of the scope and
postulate for now that I do need it; and no, I don't want to use any of Perl5
solutions. Just to focus more on Proxy itself.
What other approaches to implement laziness in Perl6?
Method based. It could either be
The real problem is that, in the absence of Proxy, rakudo can optimize a
bunch of things away because it knows it has full control of the value. But
if it encounters a Proxy, it has to assume that the Proxy might be
manipulating state outside of the current thread, or even outside of
rakudo, that
This is the first in a series of a half dozen responses to Vadim's
AttrX::Moo post that replace a couple earlier failed attempts to post here.
I apologize if there end up being repeats or my following up with several
responses is inappropriate.
Hi Vadim. I'm making this my first post because it
