sbshah97 / ds-algo-handbook Goto Github PK

Create a CONTRIBUTING.md file

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Data Structures:

1. Stacks
2. Queues
3. Trees
4. Linked Lists
5. Graphs
6. Hash

Hi @salman-bhai
I have some suggestions to improve the reach and usefulness of this repository as this concept is extremely supportive for competitive programmers and is helpful resource for ACM ICPC aspirants, but due to its name, many aspirants might not find this repository on first go.

I would like to suggest some names for the repository. Please rename the repository to something more relevant.
Suggestions:

1. ACM-ICPC-Handbook
2. DS-Algo-Handbook
3. DS-Algo-Analysis-Manual
4. Competitive-Programming-Handbook

I would also like to suggest removal of lab_assignments from the repository as it is very much irrelevant when talking about ACM-ICPC Handbooks, to make it more relevant you can Rename the folder as "Classical Problems", it would help in getting more contributions from the enthusiasts and ACM ICPC aspirants, where contributors can add up solutions for past year problems and popular classical problems of competitive programming.

Lastly, I would suggest keeping more algorithms and data structures as ACM ICPC preparation requires much more than basic ones. This link has list of many more resources that you can put up as issues to make this repository extremely useful.

I would like to hear what you have to say on these suggestions.

Cheers!

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Hey! Looks like you're on your way to your First Pull Request. You don't even need to write a single line of code for this!

Welcome to the Hacktoberfest! 😄 This is a First-Timer Issue to increase your confidence in the field of Open-Source. All you have to do is send a Pull Request (Click here to see how to send a Pull Request).

All you have to do is explain the Data Structure and an appropriate explanation for the same. Just make sure you explain the concepts in the respective Data Structure

• Linear Search
• Binary Search

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄
5. Kindly claim one Search Algorithm before moving to another!

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Hey! Looks like you're on your way to your First Pull Request. You don't even need to write a single line of code for this!

Welcome to the Hacktoberfest! 😄 This is a First-Timer Issue to increase your confidence in the field of Open-Source. All you have to do is send a Pull Request (Click here to see how to send a Pull Request).

All you have to do is explain the Sorting Algorithms and an appropriate explanation for the same. Just make sure you explain the concepts in the respective Sorting Algorithms.

• Bubble Sort
• Bucket Sort
• Heap Sort
• Insertion Sort
• Merge Sort
• Quick Sort
• Radix Sort
• Selection Sort
• Shell Sort
• Topological Sort
• Tree Sort

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄
5. Kindly claim one Sorting Algorithm before moving to another!

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Check out this link to understand better.

The array is not sorted in binary-search.cpp

Hey! Looks like you're on your way to your First Pull Request. You don't even need to write a single line of code for this!

Welcome to the Hacktoberfest! 😄 This is a First-Timer Issue to increase your confidence in the field of Open-Source. All you have to do is send a Pull Request (Click here to see how to send a Pull Request).

All you have to do is explain the Data Structure and an appropriate explanation for the same. Just make sure you explain the concepts in the respective Data Structure

• Disjoint Sets
• Hashing
• Singly Linked List
• Doubly Linked List
• Circular Linked List
• Queues
• Stacks
• Binary Search Trees
• AVL Trees
• Binary Trees
• Tries

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄
5. Kindly claim one Data Structure before moving to another!

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Sorting Algorithms:

1. Selection Sort
2. Bubble Sort
3. Merge Sort
4. Quick Sort
5. Shell Sort
6. Topological Sort

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Search Algorithms:

1. Linear Search
2. Binary Search

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Search Algorithms:

1. Linear Search
2. Binary Search

Hey! Looks like you're on your way to your First Pull Request. You don't even need to write a single line of code for this!

Welcome to the Hacktoberfest! 😄 This is a First-Timer Issue to increase your confidence in the field of Open-Source. All you have to do is send a Pull Request (Click here to see how to send a Pull Request).

All you have to do is explain the Graph Algorithm and an appropriate explanation for the same. Just make sure you explain the concepts in the respective Graph Algorithm!

• BFS
• DFS
• Dijkstra's Algorithm
• Prim's Algorithm MST
• Kruskal's Algorithm MST
• Floyd Warshall's Algorithm
• Bellman Ford's Algorithm

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄
5. Kindly claim one Graph Algorithm before moving to another!

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Hi @salman-bhai, I think it would be important to have unit tests for each of the data structure and algorithm implementations.

This would help improve the quality of the implementations since it would ensure the implementations actually work in the respective languages.

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Search Algorithms:

1. Linear Search
2. Binary Search

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

The following Algorithms need to be added:

1. BFS
2. DFS
3. Kruskal's
4. Prim's
5. Dijkstra's
6. Floyd-Warshall Algorithm

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Check out this link to understand better.

The following Algorithms need to be added:

1. BFS
2. DFS
3. Kruskal's
4. Prim's
5. Dijkstra's
6. Floyd-Warshall Algorithm

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Sorting Algorithms:

1. Selection Sort
2. Bubble Sort
3. Merge Sort
4. Quick Sort
5. Shell Sort
6. Topological Sort

The following Data Structure needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Data Structures, feel free to ask in the comments section below. 😄

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Kindly claim for the following Data Structures:

1. Stacks
2. Queues
3. Trees
4. Linked Lists
5. Graphs
6. Hash

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

The following Algorithms need to be added:

1. BFS
2. DFS
3. Kruskal's
4. Prim's
5. Dijkstra's
6. Floyd-Warshall Algorithm

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄

The following Algorithm needs to be implemented in the following languages.

• C
• C++
• Python
• Java

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.
4. Make sure you put in the proper folder. If you do not know where to push the code for the Algorithm, feel free to ask in the comments section below. 😄