http://qs321.pair.com?node_id=11117001


in reply to Re: Cor—An object system for the Perl core
in thread Cor—An object system for the Perl core

The has function is overworked ... With plain bless, parameters for object creation and object attributes were totally independent (which means you have to code it all by hand), with Moo* everything needs to occur in has (or as a fallback munged in BUILDARGS).

They're totally independent for Cor. has $data; only declares instance data. That's all. Absolutely nothing else. The optional attributes describe other aspects of the class. I worked very hard to make sure that was correct.

As an aside, even pure-Perl Cor will be faster that Moo/se, but I can't say much more about that right now.

  • Comment on Re^2: Cor—An object system for the Perl core

Replies are listed 'Best First'.
Re^3: Cor—An object system for the Perl core
by Your Mother (Bishop) on May 21, 2020 at 12:56 UTC
    As an aside, even pure-Perl Cor will be faster that Moo/se, but I can't say much more about that right now.

    *Everything* is faster than Moose so…

    For my part, the syntax and its power look nice. All seems quite well thought out; what I skimmed on the wiki sounds terrific. I would maybe still argue it’s better on the CPAN—even if there is core support necessary to go with it—before the core to gauge adoption and suitability. If it’s good—appropriate, doesn’t drag a bunch of stuff down because of core changes—it will see quick adoption and clean-up and such making it even better for the core. If not, it will avoid a lot of fights, core issues that could be rolled back, and problems going forward. I’d like to hear what people like dave_the_m think about it.

    Sidenote: This is the first I’ve heard about it and I find that a little troubling though I understand that opening everythig up to committee is a good way to prevent progress.