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
Either the documentation surrounding map_vertex should be changed to document that it is unsafe to map vertices to the same value, or values for new vertices need to be somehow loaded in the implementation. Most likely, this would necessitate switching from a map to a fold, and essentially rebuilding the whole thing, but I suspect that the map is essentially already doing this.
The text was updated successfully, but these errors were encountered:
CHANGES:
- ❗ OCamlGraph now requires OCaml >= 4.08
- ❗ [Traverse]: fixed [Dfs.fold] and [Dfs.fold_component],
which were not implementing a proper DFS
- [Classic]: new functions [cycle] and [grid]
- [Eulerian]: Eulerian paths (new module)
- [Components]: strong articulation points (see functors [Connectivity]
and [BiConnectivity]) (Timothy Bourke)
- [Dominator]: non-trivial dominators (Timothy Bourke)
- backtracking/ocamlgraph#31: fixed documentation of [map_vertex]: the supplied function
must be injective
- backtracking/ocamlgraph#110: ensure that map_vertex applies the function only once per vertex
nberth
pushed a commit
to nberth/opam-repository
that referenced
this issue
Jun 18, 2024
CHANGES:
- ❗ OCamlGraph now requires OCaml >= 4.08
- ❗ [Traverse]: fixed [Dfs.fold] and [Dfs.fold_component],
which were not implementing a proper DFS
- [Classic]: new functions [cycle] and [grid]
- [Eulerian]: Eulerian paths (new module)
- [Components]: strong articulation points (see functors [Connectivity]
and [BiConnectivity]) (Timothy Bourke)
- [Dominator]: non-trivial dominators (Timothy Bourke)
- backtracking/ocamlgraph#31: fixed documentation of [map_vertex]: the supplied function
must be injective
- backtracking/ocamlgraph#110: ensure that map_vertex applies the function only once per vertex
See this SCC contraction code for an example of how I ran into this.
Either the documentation surrounding
map_vertex
should be changed to document that it is unsafe to map vertices to the same value, or values for new vertices need to be somehow loaded in the implementation. Most likely, this would necessitate switching from a map to a fold, and essentially rebuilding the whole thing, but I suspect that the map is essentially already doing this.The text was updated successfully, but these errors were encountered: