Functional interface?

[zyrolasting]

I'm assuming that the interface is imperative to avoid making increasingly large graph copies. Still, I'd hope to have (and am willing to contribute) a functional interface if there's a way to only use memory for added vertices, edges, and properties and reuse references to existing data.

I understand some could argue that defeats the purpose of functional code in the first place, but the imperative interface tends to make the code around it imperative too. I'd like to limit that.

Are there already any plans to do this?

[stchang]

There are no plans to do this but I would be open to contributions. I think many of the algorithms would need to be reimplemented though?

[zyrolasting]

@stchang Yes. I think you and I both ended up seeing Erwig's paper about this in the Racket Slack. I realized the scope of this effort after that. Once I can read and understand that paper, I would be happy to provide a parallel implementation in this package.

[stchang]

Closing this for now but feel free to reopen with a pull request or separate issue if you have more specific ideas. Thanks!