| 1. Namespace/GFG | 1. C-Plus-Plus | |
| 2. Top Algorithms for CP | 2. Good Blog Post/Resources | |
| 3. Top Algorithms for CP | 3. Unique BSTs |
- Note: The Introduction files may contain some turtle graphics and to implement them i recommend to download Simple Codeblocks link is given above .You can also use plugin library for same.
- open Terminal and clone the repo
git clone https://github.com/Lakhankumawat/LearnCPP.git- cd over
cd LearnCPP- follow along
happy coding!
| Follow these steps | |
|---|---|
| New Algorithm | 'Please see if the algorithm is already present' |
| What to include | "Your algorithm should be efficiently written with proper code / comments / time complexity / space complexity / link to gfg or any other documentation on top in code file" |
| Where to include | Most of the algorithms are insidehereplease commit your algorithm in correct folder or discuss here before commiting for where to include |
| README | "Please check whether your directory has a README file , if there is then edit your algorithm name with link , otherwise create new one " how your README should look like |
| Follow these steps | |
|---|---|
| New Problem Statement | 'Please see if the problem is present already ? If it is do not commit your own ' |
| What to include | "Your problem statement solution should be efficiently written with proper code / comments / time complexity / space complexity / link to problem statement in code file" |
| Where to include | Most of the Problem Statements are insidehereplease commit your problem solution in correct folder or discuss here before commiting for where to include |
| README | "Please check whether your directory has a README file , if there is then edit your algorithm name with link , otherwise create new one " how your README should look like |
| Additional Context | "There are three levels of problem statement" 1-Level 1 like wise 2-Level 2 & 3-Level 3 , please include your problem statement with solution in right level you prefer |
Fond of designing README this section will be helpful to you
| Follow these steps | |
|---|---|
| New README | 'Please see if there is no README in any folder , if no ? Then please design it ' |
| What to include | "Your README should be efficiently and clearly written / link to problem statement in code file" |
| Where to include | Inside the folder where programs are residing ,discuss here before commiting for where to include |
| README | Example for README |
Please contribute using GitHub Flow. Create a branch, add commits, and open a pull request.
Please read CONTRIBUTING for details on our CODE OF CONDUCT, and the process for submitting pull requests to us.
Thanks goes to these wonderful people :
SATYAM KUMAR 💻 |
Nikita Sharma 🚧 🤔 |
Ujjwal Bansal 💻 |
Developed with ❤️ in India 🇮🇳
