go ahead... be a heretic PerlMonks

### Comment on

 Need Help??

Good question! I've been working on it to see what the real issue is. I don't have an answer for you; I'm just documenting what I've found for everyone's benefit.

First, I presume that "inherently recursive" means "cannot be rewritten to be tail-recursive". Fibonacci is an example of an inherently recursive algorithm.

```sub fibonacci {
my (\$n) = @_;
return 0 if \$n == 0;
return 1 if \$n == 1;
return sum fibonacci(\$n-2), fibonacci(\$n-1);
}

At face value, it's quite easy to make it threaded:

```sub fibonacci {
my (\$n) = @_;
return 0 if \$n == 0;
return 1 if \$n == 1;
return sum map \$_->join(),
async { fibonacci(\$n-2) },
async { fibonacci(\$n-1) };
}

But what if you wanted to limit the number of threads (perhaps to limit overhead)? One solution would be to have a pool of threads and to use them if available.

```sub fibonacci {
my (\$n) = @_;
return 0 if \$n == 0;
return 1 if \$n == 1;
return sum map \$_->get(),
async_maybe { fibonacci(\$n-2) },
async_maybe { fibonacci(\$n-1) };
}

(The above assumes closures can be shared, but it can be rewritten to not use closures.)

When implementing async_maybe (and the get of the object it returns), one must be extra careful to avoid the situation where a thread is waiting to have it's result collected.

But what if you want a worker model (perhaps to distribute the work to other machines)? Now, that's hard. One would need some kind of a callback system.

```sub fibonacci {
my (\$n) = @_;
my \$result;
process_and_wait(sub {
fibonacci_task(sub { \$result = \$_[0]; }, \$n );
});
return \$result;
}

my (\$on_complete, \$n) = @_;
return \$on_complete->(0) if \$n == 0;
return \$on_complete->(1) if \$n == 1;
my (\$x,\$y);
process(sub { fibonacci_task(sub { \$x = \$_[0] }, \$n-2) });
process(sub { fibonacci_task(sub { \$y = \$_[0] }, \$n-1) });

#TODO: The last of the two tasks to complete
#      must call \$on_complete->(\$x+\$y).

}

The TODO item is hard to do cleanly. And of course, I'm still using closures even though I think that's not an option for threads threads. Rewriting to avoid closures will likely make the code even longer.

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

• Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
• Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
• Read Where should I post X? if you're not absolutely sure you're posting in the right place.
• Posts may use any of the Perl Monks Approved HTML tags:
a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
• You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
 For: Use: & & < < > > [ [ ] ]
• Link using PerlMonks shortcuts! What shortcuts can I use for linking?

Create A New User
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (10)
As of 2018-03-23 17:34 GMT
Sections?
Information?
Find Nodes?
Leftovers?
Voting Booth?
When I think of a mole I think of:

Results (295 votes). Check out past polls.

Notices?