perl5 VS problem-solving

Configure (Permalink)

I was not signed into GitHub. I opened the permalink and it displayed fine. I opened the raw page in another tab; it was fine.

As we mentioned last week, this week we are working on a portable, symbolic link implementation that also works on Windows. You can see our progress here. To implement this, the Perl win32/win32.c source code would be greatly appreciated.

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."

First round of feature 'class'

First I noticed that there are some warning during the build emitted by one of the dependencies. As it turns out upgrading the dependency solved this issue, but the latest package of the dependency also had a minor issue. The version numbers in the different files were slightly confusing. So I reported that too.

Supply blocks may reorder flow of execution #364: solved Deadlock in supply / whenever chain #5141: fixed Simplify Supply / whenever processing order #5158: superseeded Fix rare deadlocks during supply setup #5202: merged 2023-11-24 Switch Supply.zip to a watermark approach (https://github.com/rakudo/rakudo/pull/5211rework) #5211: merged 2023-03-09 Test supply setup with a blocking recursion #833: merged 2023-11-24

I'm more leaning towards the former. you could open an issue at https://github.com/Raku/problem-solving/issues so that it won't get forgotten.

Either way, I posted the other day a problem solving issue on the topic. I think we should start looking into ways to properly supporting the mixed grammars, be it a trait-like thing (you've basically made a trait without being a trait), a token (like mine) or some other specialized regex syntax.

Perl 6 was renamed to Raku in 2019 [1], when they finally admitted to themselves that it wasn't going to be "the next Perl"

https://github.com/Raku/problem-solving/pull/89#issuecomment...

There was no admitting to themselves.

There was the personal realization that the two factions in what was then the Perl community, would never see eye to eye on what the language called "Perl 6" was. And that all of my efforts of reconciliation, such as the Perl Reunification Summit http://blogs.perl.org/users/gabor_szabo/2013/02/perl-reunifi... had been in vain.

Which lead me to open an issue https://github.com/Raku/problem-solving/issues/81 which in the end resulted in the rename to the Raku Programming Language https://raku.org .

Over time, most of the features that were a selling point for Data::Record have been rendered silly. Namely, the idea of a Tuple and Dict in core has been tossed about since writing, and the introduction of type inference for lists into core leaves most of the collections as which Data::Record is defined (Data::Record::Tuple, Data::Record::List, Data::Record::Map) with the odd edge case to cover, of which I don't feel it does a very good job of in its current release's state.

Last week, I mulled over my concerns with my implementation of IO::Resolver::Native, an abstraction for Raku's current DNS resolution behaviour. I came to the conclusion that while my ideas for a solution for problem-solving#243, followed by a solution for the problem-solving#111 that prompted that issue, followed by my ideas for the IP6NS grant that prompted those issues can be implemented separately, are not cleanly separable design-wise.

Now also as a problem solving issue: https://github.com/Raku/problem-solving/issues/280

Other than that, I'd also like to get started adding support for syntax specifying nested return types via destructuring GH issue in Rakudo. At the very least, I plan to get a PR in to Problem Solving detailing the plan – which is already basically set out in the issue, so that shouldn't be too big of a lift.

related problem-solving issue: https://github.com/Raku/problem-solving/issues/158