Update Repo #1
Merged
Update Repo #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* added code for coin change problem * added proper directory structure * added README.md for the problem
* added code for distinct ways to climb stair problem * added proper directory structure * removed file outside directory * added README.md for the problem * added README.md for the problem
* Added Heap Sort Java implementation * Revert "Added Heap Sort Java implementation" This reverts commit e2d62b2. * Add Edit Dsitance * Add Readme Change folder structure * Rename README.txt to README.md * Update README.md * Delete duplicate file
* Create doublylinkedlist.java * Update doublylinkedlist.java * Update doublylinkedlist.java
* ADD gitignore * Modified gitignore
* added code for ways to decode * added proper directory structure * added README.md for the problem
* linkedlist implementation n c++ * Update linkedlist.cpp
* Create BubbleSort.c * Reformatted * Reformatted
* Added fibonacci problem as dynamic programming example * changed folders per request * Added readme
* Create BubbleSort.cpp * Rename Sorting/Bubble Sort/Cpp/BubbleSort.cpp to Sorting/Bubble Sort/C - -/BubbleSort.cpp * Changed filename
* Added python implementation of stack * Added python implementation of stack
fixes #174
Implemented Heap Sort, Bubble Sort and Selection Sort (JS)
* Added recursive factorial in C/C++/Python/Java * Added README for factorial * Added C++ templates and longs for C and Java
* added code for longest increasing subsequence * added proper directory structure * removed file outside directory * added README.md for the problem * changed directory name * Made some style changes
…-C++ Fix for issue #228 - Insertion sort in C++
* Folder structure and Readme file. * Readme documentation. * Pseudocode for kmp in readme. * KMP algorithm implementation and readme update. * Readme pesudocode reference.
…untime (#293) The list that is to be sorted can be entered by the user at runtime. Proper and clear presentation of code for the users.
* Gradiant descent implementation. * Small fixes in implementation. Split data into x and y data vectors, instead of containing it all inside one data vector. * Fixes and readme documentation.
New information to readme file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding.
Description
Please describe what changes you have made.
For Example:
Added a file(s) named '...' that implements '...'.
Changed the algorithm for performance/readablity/bugs.
Added documentation to the algorithm
Related Issue
This project only accepts pull requests related to open issues.
If suggesting a new feature or change, please discuss it in an issue first.
If fixing a bug, there should be an issue describing it with steps to reproduce.
Please link to the issue here:
How Has This Been Tested? (Optional)
Please describe in detail how you tested your changes.
You can skip this if you have not added any tests.
Screenshots (Optional)
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Bug fix (change which fixes an issue with the algorithm)
New Algorithm (non-breaking change which adds functionality)
Documentation
Checklist:
Go over all the following points, and put an
xin all the boxes that apply.If you're unsure about any of these, don't hesitate to ask. We're here to help!
My code follows the code style of this project.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have read the CONTRIBUTING document.