Currently, the repo only contains solution's problems but are not descriptive. You can add a README.md file describing the problem or solution (if possible) in detail.

Your device hardware:

Issue details: Given the root node of a binary tree, can you determine if it's also a binary search tree? Complete the function which has parameter: a pointer to the root of a binary tree. It must return a boolean denoting whether or not the binary tree is a binary search tree. You may have to write one or more helper functions to complete this challenge.

boolean checkBST(Node root) { return checkBSTUtil(root, null, null); } private boolean checkBSTUtil(Node root, Node min, Node max){ if(root == null){ return true; } if(min != null && min.data >= root.data){ return false; } if(max != null && root.data >= max.data){ return false; } return checkBSTUtil(root.left, min, root) && checkBSTUtil(root.right, root, max); }

Log (optional):

Working solution for Insert a node at the tail of linked list - https://www.hackerrank.com/challenges/insert-a-node-at-the-tail-of-a-linked-list/problem?isFullScreen=false

A duplicate of #41 with additional commits that automatically address incorrect style, created by Restyled.

Since the original Pull Request was opened as a fork in a contributor's repository, we are unable to create a Pull Request branching from it with only the style fixes.

The following Restylers made fixes:

• clang-format

To incorporate these changes, you can either:

1. Merge this Pull Request instead of the original, or

2. Ask your contributor to locally incorporate these commits and push them to the original Pull Request

   Expand for example instructions

   ```console
   git remote add upstream https://github.com/Kvaibhav01/HackerRank-Solutions.git
   git fetch upstream pull/<this PR number>/head
   git merge --ff-only FETCH_HEAD
   git push
   ```
   

NOTE: As work continues on the original Pull Request, this process will re-run and update (force-push) this Pull Request with updated style fixes as necessary. If the style is fixed manually at any point (i.e. this process finds no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

Visit HackerRank's Data Structures website, visit the subdomains and commit new problem solutions at the repo's Data Structures folder.

Rules:

1. Solutions must be correct (obviously), I will review them before merging.
2. The solution's directory path must be according to the subdomain HackerRank provides for Data Structures. Example: /Data Structures/Subdomain name/Solution.java or /Data Structures/Subdomain name/RelevantFileName.java
3. Code can be done in any preferred language but Java and JavaScript are recommended. Someone who provides the solution in Kotlin/PHP (or any other language except recommended ones) will be considered later.
4. Code should be formatted properly. Unformatted code will be disregarded.
5. The solution you submit should be of your own.

Currently, there is no problem description file for 10 Days of Statistics.

Add a README.md file for each day problem explaining how to solve the issue, and if possible what the solution code means.

Example: For Day 0: Mean, Median and Mode, add the README file that explains above so that we have two files in the Day 0 folder; one of the actual solution and second the README file.