oodler577 / p5-sub-genius Goto Github PK

Hi Brett:

Might it be possible to show your code in operation using a GitHub action as in:

https://github.com/philiprbrenan/TreeTrek/blob/main/.github/workflows/main.yml

This provides immediate gratification for the casual observer by eliminating the need to download and install code.

• move theory and background information in to a pure .pod file
• update main POD int Sub/Genius.pm to focus on using the module in scripts, via stubby, and maybe even using fash for some deeper debugging
• remove EXPERIMENTAL status

This ability would convert a "plan" of sequentially ordered symbols, into literal Perl code that just executes each sub one after the other - passng $scope back an forth:

   # init
   my $scope =  { taco => 'tuesday' };

   # Effectively the `run_once`:
   $scope = A($scope)
   $scope = B($scope)
   $scope = C($scope)
   $scope = D($scope)
   $scope = E($scope)

   print Data::Dumper::Dumper($scope};

After run once:

$VAR = {
      taco => 'everyday',
};

Allow following to take a "max length" parameter:

• next
• init_plan
• run_any

The proper solution is to support {N} or {N,M} syntax in Perl FLAT, as bounds on *.

Show application of spawn/merge (for lack of the more clear common term but confusion in perlandia, "fork/join") - basically the SMP mode OpenMP presents

discuss what async means to Sub::Genius and what it looks like

"unweildy" in terms of:

• execution time
• state space
• redundant operations
• computer memory

Seems to be a FLAT issue, but affects Sub::Genius nonetheless.

the vision here is a thorough treatment of "concurrent" memory models and what this looks like in the context of an application using S::G

give the memory models, modules and programs may be:

• SMP oblivious - i.e., order of execution doesn't matter
• SMP aware - execution order affects results (can be leveraged for cool things)

Perl squential consistency...