Combine with petgraph somehow?

[hoijui]

Would it be possible/make sense, to use petgraph graphs as store implementations for gryf?
petgraph is aroung for longer and used more, and it has more tooling/algorithms around it (I estimate), while gryf has a nicer interface/API.
If we had the above, I could primarily use gryf in my code, but use a petgraph as storage, and used e.g. fdg-sim for layouting (for rendering).
How feasible is that, or what alternative ways for combining would you see?

[pnevyk]

It is technically possible. In a nutshell, it would mean implementing gryf traits such as Neighbors and VertexSet (see the full list of traits here) on petgraph graph types, or ideally on generic types implementing petgraph traits such as IntoNeighbors. Gryf traits are designed in a way that only a minimal implementation is necessary (sometimes with a performance penalty though, so overriding default implementations where it matters would make sense – see contains_vertex for an example where the default implementation is inefficient).

Where we would hit a blocker is probably making gryf base types/traits (e.g., IdType) work with petgraph types (i.e., NodeIndex). That would probably require direct support in gryf to overcome the orphan rule.

I would be open to adding the petgraph integration to gryf behind a feature flag. But I don't have capacity now to work on gryf. Would you be open to give it a try and open a PR?

[hoijui]

Thanks for the analysis and heads-up!
I can not say if I will do that (probably not), but if I do, I will make a PR for sure.