App-perlbrew VS Corinna

Perlbrew on github

Note that this Oracle Linux VM comes with Perl 5.26, if you want a more recent version, you could use use Perlbrew.

Install your own Perl with perlbrew, instead of using the system Perl. Then every needed dependency is installed in an isolated Perl with cpanm.

The final and most exciting way to call --init is with a Perl version number. When called with a version number, Plx will look for a Perl of the given version first in your PATH and otherwise via Perlbrew.

perlbrew is a command line tool to intall Perl on user directries. You can install any version of Perl on your user directries and use it.

Can't perlbrew be an option? AFAIK, it installs the Perl of your choice "next to" the Perl that comes with the OS, so both will continue to work.

Perl offers several libraries for managing type constraints, such as Data::Checks, Type::Tiny, and Moose. In large projects, you might encounter a mix of different type constraints, reflecting the codebase’s evolution over time. Furthermore, recent Perl versions have introduced projects like Corinna, which focuses on class features, and Oshun, which deals with value checking (with Data::Checks being a prototype from this project). Given these developments, I believed it would be useful to manage multiple type constraints through a unified interface, simplifying the process of staying up-to-date with Perl’s advancements.

this the repository of initial draft:https://github.com/Ovid/Cor

after they proposed this, people debating around this in long time.

Have you been following the developments with Perl's forthcoming OOP engine, Corinna?

You can read about some of the discussions here (that's after the BUILD/BUILDARGS debate). Unfortunately, since much of the discussion took place on IRC, and there's a policy against allowing public logging without explicit permission of the channel owners (I am not an IRC guy, so I'm not one of the channel owners), much of this valuable discussion has been lost to time. I don't wish to repeat this mistake in future projects, but I can't change the past.

I've opened a discussion about revisiting Twigils.

However, I wouldn't shelve your plans to put more time into Moose. The PR for the initial Corinna work is out and while /u/leonerduk's work is great, the PR is huge and there are a few minor issues to deal with. I do not know when the initial Corinna work will be finished and even after that, it will be a couple of years before it's considered "stable."

From the Rationale for Corinna:

It's based on years of experience being the lead designer of the Corinna project and trying to figure out how we can get a version of Moose which is safer and easier to use, including removing a lot of boilerplate. This code:

By now most of you have probably heard about the Corinna project to get modern object-oriented programming in the Perl core. The RFC has been submitted to P5P and it's a slimmed down version of the full specification. It's in seven stages, each building on the last.