Jonathan Beard

Yeah, I like the symmetry...however any thoughts on coding up => as an overload? That is the real issue with that syntax. The two simpler candidates are of course: =....

Hmm, I like the renaming idea. I'll comment on the others in a bit, how about "ramify" :) or "diverge" didn't want to use fork since there are too many...

broadcast might work.... On Tue, Apr 19, 2016 at 1:34 PM, adishavit [email protected] wrote: > I don't think we need to invent new names. > > What does e.g. TBB...

I like all those ideas...basically this is a tuple, but we also have to tie in the concept of kernels and ports. each kernel within the tuple must have a...

Sorry it's taken awhile to get back to you, it's been a very busy few weeks. Short answer, by design, I've left as little state between kernels as possible. So...

Hah. I'm left with the thought of adding a nervous system with a lightweight side channel to register messages for specific other kernels. The catch, for this, given RaftLib's construction...

This one, I'm gonna have to double check on. It should work, but I wanna check my notes in the code to be sure. I've been spending a lot of...

You know, that's a very good point. Any chance you could provide a test case for the second scenario and a contrived example to provide for the examples folder? Then...

Currently that is the expected behavior. The issue with the old parser was the syntax for doing just this. Given that it is essentially a DSL, and so there are...

I actually like the iomanip style best, however if you have multiple incoming ports to "b" then it would seem you have to reiterate on ever stream...or perhaps one is...