@profoundlynerdy I don’t know anything about #Rakudo’s internals, but Is there any conceivable way for a language-neutral subset of #RakuLang #regexes to be based on or share its code rather than reimplement them?

The subset might omit things like code interpolation. Or is it all-or-nothing?

It would be a nice teaser for the full power of Raku grammars, kind of like how #iTunes for Windows was #SteveJobs’ offer of “a glass of water to somebody in hell.” https://a.co/5J0CTSL

@sotolf @benjaminhollon

That's why I appreciate the fact that #Rakudo implements "use strict;" by default.

I don't honestly know the ins & outs of the *insanely* protracted political battle of Perl "6," but I'm very sad that the community ultimately rejected Perl 6, spinning it off as a new language with a new name, making some minor changes to #Perl 5 & calling it Perl 7. :'(

Speaking of which, is Perl 7 coming out any time soon, or is IT going to take 20 years as well? %)

Pour passer de bon moment avant la fin de l’année, vous avez le calendrier de l’avent de #Raku

https://raku-advent.blog/2020/12/01/day-1-why-raku-is-ideal-for-advent-of-code/

#Rakudo #perl #perl6

Anybody interested in getting their feet wet optimizing #regex code based on a not-terribly-complicated AST? It'd be for #rakudo #perl6. I wrote a lengthy mail for how to get started and what to look for if you want, it's here on the perl6 #compiler mailing list:

https://www.nntp.perl.org/group/perl.perl6.compiler/2019/08/msg18330.html