Paul Hinze b45f53eef4 dag: fix ReverseDepthFirstWalk when nodes remove themselves ...

The report in #7378 led us into a deep rabbit hole that turned out to
expose a bug in the graph walk implementation being used by the
`NoopTransformer`. The problem ended up being when two nodes in a single
dependency chain both reported `Noop() -> true` and needed to be
removed. This was breaking the walk and preventing the second node from
ever being visited.

Fixes #7378

2016-07-15 13:43:28 -06:00

..

dag_test.go

dag: fix ReverseDepthFirstWalk when nodes remove themselves

2016-07-15 13:43:28 -06:00

dag.go

dag: fix ReverseDepthFirstWalk when nodes remove themselves

2016-07-15 13:43:28 -06:00

edge_test.go

dag: Remove, RemoveEdge, DownEdges, UpEdges

2015-02-19 12:07:54 -08:00

edge.go

dag: export more things

2015-02-19 12:08:07 -08:00

graph_test.go

dag: add HasVertex, HasEdge

2016-01-14 13:52:01 -08:00

graph.go

dag: Fix graph printing type mismatch

2016-07-15 13:42:08 -06:00

set.go

dag: use hashcodes to as map key to edge sets

2015-10-27 11:58:34 -07:00

tarjan_test.go

dag: Remove, RemoveEdge, DownEdges, UpEdges

2015-02-19 12:07:54 -08:00

tarjan.go

dag: fix walk order issue, scc issues

2015-02-19 12:07:55 -08:00