Skip to content

Commit 3e08e8e

Browse files
committed
readme
1 parent e28a556 commit 3e08e8e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
A pretty good implementation of Dijkstra's shortest-path algorithm for Deno.
44

5-
If you ever run into a problem that can be represented as a graph where the solution has something to do with finding the shortest path between nodes, this algorithm is magical. It is well worth the time to learn how to use it.
5+
If you ever run into a problem that can be represented as a graph where the solution has something to do with finding the shortest path between nodes, this algorithm is nothing short of magical. It is well worth the time to learn how to use it, even if you don't really understand how the algorithm works.
66

77
This implementation of Dijkstra'a algorithm is able to process large in-memory graphs. It will perform
88
reasonably well even when the number of edges is in the millions. The performance is `O(n*log(n))`.
@@ -22,7 +22,7 @@ Dijkstra's algorithm actually calculates the shortest paths from the start node
2222

2323
You can reverse the direction of the calculation. Calling it "start node" is just a convention. It can also be an end node if you set up the graph correctly.
2424

25-
This implementation supports cloning the solver and extending its graph dynamically. Graph generation can be expensive. For many applications, most of the graph can be reused, with a only a small portion needing to be dynamic.
25+
This implementation supports cloning the solver and extending its graph dynamically. Graph generation can be expensive. For many cases, most of the graph can be reused, with a only a small portion needing to be dynamic.
2626

2727
# Example
2828

0 commit comments

Comments
 (0)