Elijah ben Izzy

> Yes, that is correct. Providing functionality for (2) and (4) would let me do a lot > > > For attaching metadata to those "undefined/user-defined" nodes -- before we...

OK, inspired by @jdonaldson's hamilton-like framework, I'm curious what could happen if we use chunking. Going to walk through a few different UIs I've been mulling over that would fit...

OK, latest API proposal -- feel free to react/comment. Planning to scope/implement shortly. Note these are just adaptations of the above. ## Two primary use-cases we want to handle: 1....

More edge cases: 1. Something outside a `Sequential/Collect` group depends on something inside it (this is actually not an edge case, this is dangling group) 2. Two collects on the...

Ok, I think I get what's happening. It's a side-effect, so I think we want to model it as so... I think getting it to recompute every time might be...

Yep -- got it. Ok, so I get what you're doing/asking, but I'm not 100% convinced this is the right solution to the original problem. Of two minds: ### Con:...

> My use-case isn't a dataframe problem so I understand if it doesn't fit the Hamilton philosophy. Specifically, I have to instantiate a `docx.Document` and pass it a template from...

> Just thinking through all the ways and what the code would look like -- here's the infinite generator way you describe (sorry had to write it out): > >...

> FWIW I had this same need in my own framework. I attached a handle to the generator for each method field, and it autowired itself with upstream function arguments...

> Ok, I'm sold on the name if it has anything to do with Alexander Hamilton. Graph connections are a bonus. :) > > I'll put the code together in...