Elijah ben Izzy

(intended) fix for the immediate issue [here](https://github.com/DAGWorks-Inc/hamilton/pull/144), this is a follow-up.

Ok, I think we can clarify this quite a bit -- currently it requires some details of how the system works. The name in the materializer is the name of...

This is great! Also awesome illustration -- did you do that by hand? An interesting point to note -- `feature_5` feels ambiguous to me -- it depends on both feature_2...

Hey @bryangalindo -- a thought on a feature that might be helpful. Here's an outline of what the API should look like -- the data saver/materialization implementatino should support this....

OK, so no inherent reason why this should work -- its an implementation detail that it doesn't. That said, the implementation is a little complex, and the more "hamiltonian" way...

> 🤔 I don't recall why we put `inplace=True` (sigh, commit message doesn't mention 🤦 ). Might be an easy fix as you suggest. Yep, agreed, I think @amosaikman you...

> > That's a fair argument. I guess it goes to whether or not you agree with Pandera's approach of validating and coercing or validating and filtering as a single...

> Obviously it's entirely up to you guys what you do, but from a user perspective the following makes sense to me: > > * a change that precludes silent...

OK, this is interesting. Let me make sure I get your use-case: - you want to be able to know, programmatically, which nodes are already *in* the DAG and which...

> > Cool. @gravesee how do you want to expose that information to your users? (Just thinking if there's more functionality needed, etc.) > > More for developers to be...