SccsConstruction in rustc_data_structures::graph::scc - Rust (original) (raw)

Struct SccsConstruction

Source

struct SccsConstruction<'c, 'a, G, A>

where
    G: DirectedGraph + Successors,
    A: Annotations<G::Node>,

{
    graph: &'c G,
    node_states: IndexVec<G::Node, NodeState<G::Node, A::SccIdx, A::Ann>>,
    node_stack: Vec<G::Node>,
    successors_stack: Vec<A::SccIdx>,
    duplicate_set: FxHashSet<A::SccIdx>,
    scc_data: SccData<A::SccIdx>,
    annotations: &'a mut A,
}

The state of each node; used during walk to record the stack and after walk to record what cycle each node ended up being in.

The stack of nodes that we are visiting as part of the DFS.

The stack of successors: as we visit a node, we mark our position in this stack, and when we encounter a successor SCC, we push it on the stack. When we complete an SCC, we can pop everything off the stack that was found along the way.

A set used to strip duplicates. As we accumulate successors into the successors_stack, we sometimes get duplicate entries. We use this set to remove those – we also keep its storage around between successors to amortize memory allocation costs.

Source§

Source

Identifies SCCs in the graph G and computes the resulting DAG. This uses a variant of Tarjan’s algorithm. The high-level summary of the algorithm is that we do a depth-first search. Along the way, we keep a stack of each node whose successors are being visited. We track the depth of each node on this stack (there is no depth if the node is not on the stack). When we find that some node N with depth D can reach some other node N’ with lower depth D’ (i.e., D’ < D), we know that N, N’, and all nodes in between them on the stack are part of an SCC.

Additionally, we keep track of a current annotation of the SCC.

Source

Source

Inspect a node during the DFS. We first examine its current state – if it is not yet visited (NotVisited), return None so that the caller might push it onto the stack and start walking its successors.

If it is already on the DFS stack it will be in the stateBeingVisited. In that case, we have found a cycle and we return the depth from the stack.

Otherwise, we are looking at a node that has already been completely visited. We therefore return WalkReturn::Completewith its associated SCC index.

Source

Fetches the state of the node r. If r is recorded as being in a cycle with some other node r2, then fetches the state of r2 (and updates r to reflect current result). This is basically the “find” part of a standard union-find algorithm (with path compression).

Source

Walks a node that has never been visited before.

Call this method when inspect_node has returned None. Having the caller decide avoids mutual recursion between the two methods and allows us to maintain an allocated stack for nodes on the path between calls.

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 168 bytes