heffalump / loom Goto Github PK

There's heavy duplication between algorithms and alg-generic, (of interface, not of code.) e.g. pre-traverse in algorithms takes a graph, in alg-generic takes a neighbour function and start vertex.

It would be more convenient to have one single namespace, and in each function, allow the user to either pass in a graph, or seq of vertices and a neighbour function.

The rationale behind fly-graphs is to have graphs that can be created from neighbour functions, etc. The resulting graph is read-only (not just immutable), and the only apparent purpose is to permit the user to then run an algorithm (DFS, etc) on the graph.

But the user can already do this more easily by directly running algorithms in alg-generic on the neighbour function, etc.