setzer22

> Sorry for my very rudimentary crash report. It really helps, so don't apologise! :smile: I'm glad you took your time to try this out at such an early stage....

> Currently DataType's decide whether or not we can feed them with a Eq implementation, so I can't accept Vector's into a VectorList input. I think this raises an excellent...

Just a heads up, I pushed a minor fix in #36 that will likely conflict with this PR. The code needs to be adapted so that when a node is...

> After looking over the existing PR and making a vain attempt to merge `main` into this branch, I think I'd like to start from a fresh slate and make...

@gmorenz I think you may be right :thinking: I was just playing around in blender and I the same thing never bothered me there. The other two are still issues...

Pull request #40 is going to fix these issues.

This library is mainly about creating and displaying node graphs using `egui`. Execution semantics is up to the user, so the meaning of a loop should not be defined by...

> This is because there are no applications that allow infinite loops (and even if there were, they could not be implemented in this library). What I mean is that...

Indeed, that would be quite useful. It's good that more people are using the library so we can test it against a variety of use case :slightly_smiling_face: This didn't come...

Indeed, my original idea was to always go Output -> Input, which is the natural order you'd fetch dependencies from, so `iter_connections` is kind of backwards. Since `InputId` and `OutputId`...