Browse by type

| CppNuts | Codecademy | Leetcode |
| The Cherno | johnmcfarlane/begin(C++) | HackerRank |
| ChiliTomatoNoodle | ratansingh98/CPP-Learning | CodeChef |
| Bo Qian | sahilbansal17/Get_Better_at_CP_in_2_Months | CodeForces |
| CodeBlocks | Visualisze algorithms through animations | Learn CPP |
| VS Code | CP Algorithms | CF Blog : Resources for cpp |
| Follow Steps | Get Started |
|---|---|
![]() |
![]() |
![]() |
![]() |
| 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 | please commit your algorithm in the correct folder or discuss[here](https://github.com/Lakhankumawat/LearnCPP/discussions/7)before committing to where to include` |
| README | "Please check whether your directory has a README file, if there is then edit your algorithm name with a link, otherwise create a 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 the correct folder or discuss here before committing for where to include |
| README | "Please check whether your directory has a README file, if there is then edit your algorithm name with a link, otherwise create a new one " how your README should look like |
| Additional Context | "There are three levels of problem statement" 1-Level 1 `likewise 2-Level 2 & 3-Level 3, please include your problem statement with a solution in the right level you prefer |
STL, follow the same approach as AlgorithmsFond 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, if yes? Then please edit it accordingly to your contribution and follow the guidelines '|
| 🤔 What to include |"Your README should be efficiently and written / link to problem statement in README at the top" see exmaple |
| ✅ Must Contain | 1. and explain in brief about addition 2. An Image of addition i.e how it works 3. Mention the Pseudo Code 4. Time and Space Complexities 5. Advantages 6. Disadvantages |
| 🪧 Where to include |Inside the folder where programs are residing, discuss here before committing to where to include|
contributing guidelines if you're interested in helping!| # | Problem Statement & Explanation | Solution |
|---|---|---|
| 1 | Array Operations | Solution |
| 2 | Antispiral Matrix | Solution |
| 3 | Counting Divisibl eSubstrings | Solution |
| 4 | First Negative in Every Window | Solution |
| 5 | Maximum Sum Subarray | Solution |
| 6 | Missing and Repeating Number | Solution |
| 7 | Peak in 1D Array | Solution |
| 8 | Prefix Sum | Solution |
| 9 | Reversing of Array | [Solution](https://github.com/Lakhankumawat/LearnCPP/blo |
$ claude mcp add LearnCPP \
-- python -m otcore.mcp_server <graph>