Skip to content

Commit

Permalink
Merge pull request #480 from evenfurther/explicit-link
Browse files Browse the repository at this point in the history
fix(doc): remove useless explicit links
  • Loading branch information
samueltardieu authored Nov 29, 2023
2 parents d60c026 + ec7788e commit 75de221
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 11 deletions.
2 changes: 1 addition & 1 deletion src/directed/bfs.rs
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,7 @@ where
}
}

/// Struct returned by [`bfs_reach`](crate::directed::bfs::bfs_reach).
/// Struct returned by [`bfs_reach`].
pub struct BfsReachable<N, FN> {
i: usize,
seen: FxIndexSet<N>,
Expand Down
2 changes: 1 addition & 1 deletion src/directed/dfs.rs
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ where
}
}

/// Struct returned by [`dfs_reach`](crate::directed::dfs::dfs_reach).
/// Struct returned by [`dfs_reach`].
pub struct DfsReachable<N, FN> {
to_see: Vec<N>,
seen: HashSet<N>,
Expand Down
19 changes: 10 additions & 9 deletions src/directed/topological_sort.rs
Original file line number Diff line number Diff line change
Expand Up @@ -131,15 +131,16 @@ where
/// - `nodes` is a collection of nodes.
/// - `successors` returns a list of successors for a given node.
///
/// This function works like [`topological_sort`](self::topological_sort), but
/// rather than producing a single ordering of nodes, this function partitions
/// the nodes into groups: the first group contains all nodes with no
/// dependencies, the second group contains all nodes whose only dependencies
/// are in the first group, and so on. Concatenating the groups produces a
/// valid topological sort regardless of how the nodes within each group are
/// reordered. No guarantees are made about the order of nodes within each
/// group. Also, the list of `nodes` must be exhaustive, new nodes must not be
/// returned by the `successors` function.
/// This function works like [`topological_sort`], but rather than
/// producing a single ordering of nodes, this function partitions the
/// nodes into groups: the first group contains all nodes with no
/// dependencies, the second group contains all nodes whose only
/// dependencies are in the first group, and so on. Concatenating the
/// groups produces a valid topological sort regardless of how the
/// nodes within each group are reordered. No guarantees are made
/// about the order of nodes within each group. Also, the list of
/// `nodes` must be exhaustive, new nodes must not be returned by the
/// `successors` function.
///
/// The function returns a collection of groups if there are no cycles in the
/// graph and an error otherwise.
Expand Down

0 comments on commit 75de221

Please sign in to comment.