You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be handy for the documentation to confirm the expected time and space complexity of the functions in fgl. Given that all the functions operate over instances of Graph (and friends) rather than concrete types these bounds might have to be given in terms of the number of calls the Graph's member functions, or given in terms of an idealized implementation of Graph.
This is particularly useful given the relative complexity of determining this information in Haskell.
The text was updated successfully, but these errors were encountered:
I'm not sure how feasible this will be though, as a lot of it starts to become "this is whatever the complexity of that function in the type class is" style :s
Not that I know of. They also have similar complexities (IIRC, apart from noNodes, the only difference is that PatriciaTree has better constants albeit with a possible pathological case that shouldn't occur in actual usage).
I'm wanting to make a release today or tomorrow with the QuickCheck version bump, so I may delay finishing this until a better model presents itself.
It would be handy for the documentation to confirm the expected time and space complexity of the functions in
fgl
. Given that all the functions operate over instances ofGraph
(and friends) rather than concrete types these bounds might have to be given in terms of the number of calls theGraph
's member functions, or given in terms of an idealized implementation ofGraph
.This is particularly useful given the relative complexity of determining this information in Haskell.
The text was updated successfully, but these errors were encountered: