Skip to content

Fix runtime for backtracking #4663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Kevin-Jonaitis
Copy link

Time & Space Complexity for the "Backtracking" solution is incorrect.

It is stated as:

O(m∗n∗4^t+s). Where m is the number of rows, n is the number of columns, t is the maximum length of any word in the array and s is the sum of the lengths of all the words.

However, this is looser-bound time complexity for the Backtracking (Trie) and Backtracking (Trie + Hash Set)(those bounds are slightly different than O(m∗n∗4^t+s) but are correct).

For "Backtracking", the solution should be:

O(w * m∗n∗4^t).

Reasoning:

In the base backtracking solution, we iterate over every word, and for every word, we try to find a solution. So we need the w component, where w is the number of words we're checking for.

Additionally, we arn't creating a trie in the standalone backtracking solution, so the "+ s" component should not be included.

Finally, we use the tighter bound of 4 * 3^t-1 to be in line with the other solution runtimes. This value comes from the fact that we have 4 options on our first search of the board, but because we don't want to backtrack to the option we just chose, we have 3 remaining options, hence the * 3 component.. the t -1 indicates we've already used one letter from our longest word(t).

  • File(s) Modified :articles/search-for-word-ii.md
  • Language(s) Used: English

Important

Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant