summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorditam <ditam@users.noreply.github.com>2017-10-15 20:21:07 +0200
committerditam <ditam@users.noreply.github.com>2017-10-15 20:21:07 +0200
commitc174cb0829e3b1e92c9cf86a8dc0c0f77b95295d (patch)
treef7202a41196840b688cfb91e887ea12fa0b96f7a
parent8612e00b9f26feafcb531609f0ab0ec61ea06dd0 (diff)
add backticks to escape markdown formatting characters
-rw-r--r--dynamic-programming.html.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/dynamic-programming.html.markdown b/dynamic-programming.html.markdown
index 7df367e7..4db8e92e 100644
--- a/dynamic-programming.html.markdown
+++ b/dynamic-programming.html.markdown
@@ -26,7 +26,7 @@ The Longest Increasing Subsequence problem is to find the longest increasing sub
First of all we have to find the value of the longest subsequences(LSi) at every index i with last element of sequence being ai. Then largest LSi would be the longest subsequence in the given sequence. To begin LSi is assigned to be one since ai is element of the sequence(Last element). Then for all `j` such that `j<i` and `aj<ai`, we find Largest LSj and add it to LSi. Then algorithm take *O(n2)* time.
Pseudo-code for finding the length of the longest increasing subsequence:
-This algorithms complexity could be reduced by using better data structure rather than array. Storing predecessor array and variable like largest_sequences_so_far and its index would save a lot time.
+This algorithms complexity could be reduced by using better data structure rather than array. Storing predecessor array and variable like `largest_sequences_so_far` and its index would save a lot time.
Similar concept could be applied in finding longest path in Directed acyclic graph.