Skip to content
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

Fix Non Recursive Depth First Search #2207

Open
wants to merge 3 commits into
base: master
from

Conversation

@marcoscannabrava
Copy link
Contributor

marcoscannabrava commented Jul 17, 2020

Describe your change:

  • Add an algorithm?
  • Fix a bug or typo in an existing algorithm?
  • Documentation change?

Checklist:

  • I have read CONTRIBUTING.md.
  • This pull request is all my own work -- I have not plagiarized.
  • I know that pull requests will not be merged if they fail the automated tests.
  • This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
  • All new Python files are placed inside an existing directory.
  • All filenames are in all lowercase characters with no spaces or dashes.
  • All functions and variable names follow Python naming conventions.
  • All function parameters and return values are annotated with Python type hints.
  • All functions have doctests that pass the automated testing.
  • All new algorithms have a URL in its comments that points to Wikipedia or other similar explanation.
  • If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.
  • The algorithm was passing tests but was exploring the vertices in a breadth-first approach even though it was using a stack.
  • I can add an issue to implement a test for this in the future since the current test only checks the final output but not the search method itself.
@TravisBuddy
Copy link

TravisBuddy commented Jul 17, 2020

Hey @marcoscannabrava,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 5861b5e0-c832-11ea-ab6f-3547fdb4f9a3
@TravisBuddy
Copy link

TravisBuddy commented Jul 17, 2020

Hey @marcoscannabrava,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: de28a1b0-c838-11ea-ab6f-3547fdb4f9a3
@cclauss
Copy link
Member

cclauss commented Aug 11, 2020

Does the doctring at the top of the file match the new code?

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

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.