1,154 karma · joined January 23, 2018
So I guess one could say that Raku parsing is usually static, but it does not need to be.
The Perl world has solved this by renaming Perl 6 to Raku (https://raku.org using the #rakulang tag on social media).
I don't know about Oil, and if I understand your use of "statically parsed" correctly, Raku is not statically parsed. A "use" statement can affect how Raku parses source code from there on, see e.g. the OO::Monitors module that adds a "monitor" keyword.
But even simpler, adding an operator changes the grammar. For instance, adding a postfix ! operator for faculty, can be as simple as:
sub postfix:<!>(\value) { [*] 1 .. value }
say 5! # 1201. There was no Perl yet when I read K&R. 2. "Programming Perl" was more fun.
The smart-matching in Raku (formerly known as Perl 6) is asymmetric and customizable. If you write:
a ~~ b
you are effectively executing: b.ACCEPTS(a)
In other words, the right hand side of the smart-match is responsible for accepting the left hand side. So as a developer of a class, you can add your own ACCEPTS (multi-)method to govern how your class will handle smart-matching. $_ the topic
$/ result of the last match
$! the last exception caught
An overview: https://docs.raku.org/language/5to6-perlvarIn my opinion, the failure is in the timing of the process, and keeping the Perl community involved in the process.
This is probably going to change in the next language revision of Raku. See https://github.com/Raku/problem-solving/blob/master/solution... for the nitty gritty.