update

Author: nishantc1527

.gitattributes

@@ -1,76 +1,76 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [email protected]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.gitignore

@@ -1,25 +1,25 @@
-# Contributing
-
-This repository is welcome to contributing. There are tons of stuff to add, some easy and some hard. If you want something to contribute, look at the issues page.
- 
-To encourage contributing, I developed a fun little game. Every time you contribute, you get points. I'll talk about what score you get and all the details, 
-but first, what is the use of the score? The more score you get, you get to put your name higher on the leaderboard in the section below. And what is the point
-of the leaderboard? Right under your name, you get to advertise any repository, project, etc... you want. Here is a quick privilege list (I will update it now
-and then when I feel something can be made better).
-
-5 points: Share a project.
-20 points: Add a description.
-Every 20 points, add another project with a description.
-(the rest is for you to add in [this issue](https://github.com/nishantc1527/Algorithms/issues/3))
-
-Okay, now, how many points do you get for contributing? When you pick something from [the issues](https://github.com/nishantc1527/Algorithms/issues), the issue
-will specify the number of points you get. Sometimes, it will be a concrete number, but sometimes, it will be a range (for example, 5 - 10) and you get rewarded
-depending on the quality of your pull request. Even in the issues with concrete numbers, if you go above and beyond and do a fantastic job I might reward more.
-If you leave out some stuff or leave bugs, I will ask if you want to except fewer points or fix it. If you decide to just except fewer points, then I will open
-another issue for that.
-
-But what if you found something that wasn't in the issues? Then, submit the pull request anyways, and I will determine the points myself.
-
-Now that I have the game cleared up, I would recommend some easy issues. [Improving explanations](https://github.com/nishantc1527/Algorithms/issues/4) would probably
-be the best place to start, then adding privileges. However, you can always look into the [issues](https://github.com/nishantc1527/Algorithms/issues) page for more
-stuff.
+# Contributing
+
+This repository is welcome to contributing. There are tons of stuff to add, some easy and some hard. If you want something to contribute, look at the issues page.
+ 
+To encourage contributing, I developed a fun little game. Every time you contribute, you get points. I'll talk about what score you get and all the details, 
+but first, what is the use of the score? The more score you get, you get to put your name higher on the leaderboard in the section below. And what is the point
+of the leaderboard? Right under your name, you get to advertise any repository, project, etc... you want. Here is a quick privilege list (I will update it now
+and then when I feel something can be made better).
+
+5 points: Share a project.
+20 points: Add a description.
+Every 20 points, add another project with a description.
+(the rest is for you to add in [this issue](https://github.com/nishantc1527/Algorithms/issues/3))
+
+Okay, now, how many points do you get for contributing? When you pick something from [the issues](https://github.com/nishantc1527/Algorithms/issues), the issue
+will specify the number of points you get. Sometimes, it will be a concrete number, but sometimes, it will be a range (for example, 5 - 10) and you get rewarded
+depending on the quality of your pull request. Even in the issues with concrete numbers, if you go above and beyond and do a fantastic job I might reward more.
+If you leave out some stuff or leave bugs, I will ask if you want to except fewer points or fix it. If you decide to just except fewer points, then I will open
+another issue for that.
+
+But what if you found something that wasn't in the issues? Then, submit the pull request anyways, and I will determine the points myself.
+
+Now that I have the game cleared up, I would recommend some easy issues. [Improving explanations](https://github.com/nishantc1527/Algorithms/issues/4) would probably
+be the best place to start, then adding privileges. However, you can always look into the [issues](https://github.com/nishantc1527/Algorithms/issues) page for more
+stuff.

CODE_OF_CONDUCT.md

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2020 nishantc1527
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2020 nishantc1527
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

Contributing.md

@@ -1,61 +1,61 @@
-# C++ Users
-
-There is a MakeFile for every C++ section. All testing is done with Google Test. You don't need to download Google Test yourself.
-
-# Running Files With CMake (Recommended)
-
-Go to the directory with the `CMakeLists.txt` file. Then make the CMake output directory using this:
-
-    mkdir cmake-build-debug # you can call it whatever you want, but this name is git-ignored
-    cd cmake-build-debug
-    
-Then run the CMake.
-
-    cmake ../
-    cmake --build .
-    
-Then run the CMake project.
-
-    ./Algorithms
-
-# Running Files Without CMake
-
-Note that without CMake, you can't run tests.
-
-To compile a file, use this command:
-
-    g++ <path-to-file> -o out
-    
-You can replace ```out``` with whatever you want, and you can even delete the whole ```-o out``` part. If you choose to delete ```-o out```,
-then you have to do the next step differently.
-
-Run the newly made exe file with this:
-
-    ./out
-    
-If you replaced ```out``` with something else, replace it here to. If you didn't add the ```-o out``` part, replace it with this:
-
-    ./a
-
-# [Source Code](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp)
-
-## [Data Structures](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures)
-
-### [Trees](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees)
-
-#### [Binary Search Trees](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/binarysearchtrees)
-
-* [Binary Search Tree](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/binarysearchtrees/binarysearchtree)
-
-#### [Trie](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/trie)
-
-* [Trie](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/trie)
-
-## [Sorting](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting)
-
-* [Bubble Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/bubblesort)
-* [Heap Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/heapsort)
-* [Insertion Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/insertionsort)
-* [Merge Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/mergesort)
-* [Quick Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/quicksort)
+# C++ Users
+
+There is a MakeFile for every C++ section. All testing is done with Google Test. You don't need to download Google Test yourself.
+
+# Running Files With CMake (Recommended)
+
+Go to the directory with the `CMakeLists.txt` file. Then make the CMake output directory using this:
+
+    mkdir cmake-build-debug # you can call it whatever you want, but this name is git-ignored
+    cd cmake-build-debug
+    
+Then run the CMake.
+
+    cmake ../
+    cmake --build .
+    
+Then run the CMake project.
+
+    ./Algorithms
+
+# Running Files Without CMake
+
+Note that without CMake, you can't run tests.
+
+To compile a file, use this command:
+
+    g++ <path-to-file> -o out
+    
+You can replace ```out``` with whatever you want, and you can even delete the whole ```-o out``` part. If you choose to delete ```-o out```,
+then you have to do the next step differently.
+
+Run the newly made exe file with this:
+
+    ./out
+    
+If you replaced ```out``` with something else, replace it here to. If you didn't add the ```-o out``` part, replace it with this:
+
+    ./a
+
+# [Source Code](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp)
+
+## [Data Structures](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures)
+
+### [Trees](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees)
+
+#### [Binary Search Trees](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/binarysearchtrees)
+
+* [Binary Search Tree](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/binarysearchtrees/binarysearchtree)
+
+#### [Trie](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/trie)
+
+* [Trie](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/datastructures/trees/trie)
+
+## [Sorting](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting)
+
+* [Bubble Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/bubblesort)
+* [Heap Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/heapsort)
+* [Insertion Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/insertionsort)
+* [Merge Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/mergesort)
+* [Quick Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/quicksort)
 * [Selection Sort](https://github.com/nishantc1527/Algorithms/tree/master/src/main/cpp/sorting/selectionsort)