Contributing Guidelines

Thanks for taking the time to contribute to this project. Before making PRs, please note the following:

A few norms you should follow

Proper intendation is must!
Include ample comments so that code is understandable and easy to follow.
Mention the complexity of a function in a comment.

Time complexity :
Space complexity :

Place your code in right directory.
Give your files names that are relevant and meaningful.

You may add your solved questions on spoj, codechef, hackerearth, hackerrank and codeforces.

First line of your code must begin with a comment mentioning the link of the question
Place the solutions in seperate folder "ques" in relevant directory

Best Practices for opening a Pull Request

Give the PR a meaningful name.
For e.g. 'Fixes #(issue-number): PR name, fixing the particular bug' (without commas)
There should be always 1 commit for 1 PR.
If there are more than 1 commit in a PR, squash them.
Pull Request details should be descriptive.
Commit message should meaningful.