Add CONTRIBUTING.md & Update README.md

CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# Contributing to bst-rs
+
+Thank you for your interest in contributing to this project! I really appreciate it!
+
+# Got a Question? 
+
+Please raise an issue with the `question` label. This ensures that bugs are separated from genuine questions.
+
+# Found an Issue or Bug? 
+
+Please raise an issue on if you think you have found any issues or bugs. Even better, it would be great 
+to submit a Pull Request including the fix. 

README.md

@@ -3,32 +3,111 @@
 > Recursive & Iterative Binary Search Tree Implementations within Rust
 
 ## Table of Contents
+
 - [Personal Goals](#Personal-Goals)
-- [Usage](#Usage)
+- [About](#About)
+- [Quick Start](#Quick-Start)
 - [License](#License)
+- [Contributing](#Contributing)
 - [Inspiration](#Inspiration)
 
-## Personal Goals 
+## About
+
+This crate contains Recursive & Iterative Binary Search Tree Implementations. All common operations are included along
+with common traversal iterators.
+
+All elements within the Binary Search Trees _must_ implement
+the [Ord](https://doc.rust-lang.org/core/cmp/trait.Ord.html) trait.
+
+It is also important to note that [RecursiveBST](src/lib.rs) is more likely to `blow the stack.`
+For more information on why that is the case, please read have a look at
+[The Story of Tail Call Optimizations in Rust.](https://seanchen1991.github.io/posts/tco-story/)
+
+## Personal Goals
+
+I have made this library with the personal goals of learning and solidifying concepts such as `ownership`, `borrowing`
+, `generics` and `lifetimes`. I cannot promise that the implementations are particularly efficient, or if they are, it
+was not at the forefront of my mind.
+
+That being said, there are some areas I would love to improve/include:
+
+- [ ] Write Rust more idiomatically.
+- [ ] Implement a `pretty_print()` function to display the binary search trees nicely.
+- [ ] Implementing the Drop trait for iterative node cleanup.
+- [ ] Pre-allocating space on the heap for nodes to reduce inefficiency of inserts.
+
+I'm more than happy to accept (and encourage) contributions if anyone is kind enough to do so. (Please look
+at [CONTRIBUTING!](#Contributing))
 
-One of the main motivations for starting this is to fully grasp the following concepts
+## Quick Start
 
-- [x] Ownership/Borrowing
-- [x] Generic Traits
-- [x] Lifetimes
+```rust
+use bst_rs::{BinarySearchTree, IterativeBST, RecursiveBST};
 
-I am now more confident programming around these concepts and can discuss and reason
-about different implementations.
+// Create new empty binary search trees
+let mut iterative_bst = IterativeBST::new();
+assert!(iterative_bst.is_empty());
 
-## Usage 
+let mut recursive_bst = RecursiveBST::new();
+assert!(recursive_bst.is_empty());
 
-TODO
+// Insert elements (no duplicates are allowed)
+iterative_bst.insert(10);
+iterative_bst.insert(10);   // Element is not inserted
+iterative_bst.insert(5);
+iterative_bst.insert(2);
+iterative_bst.insert(15);
+iterative_bst.insert(25);
 
-## License 
+assert_eq!(iterative_bst.size(), 5);
+recursive_bst.insert(10);
+recursive_bst.insert(10);   // Element is not inserted
+recursive_bst.insert(5);
+recursive_bst.insert(2);
+recursive_bst.insert(15);
+recursive_bst.insert(25);
+assert_eq!(recursive_bst.size(), 5);
+
+// Check if element exists
+assert!(iterative_bst.contains(&5));    // true
+assert!(!iterative_bst.contains(&0));   // false
+assert!(recursive_bst.contains(&5));    // true
+assert!(!recursive_bst.contains(&0));   // false
+
+// Remove elements
+iterative_bst.remove(&10);
+iterative_bst.remove(&50); // No change to tree as element does not exist
+assert_eq!(iterative_bst.size(), 4);
+
+recursive_bst.remove(&10);
+recursive_bst.remove(&50); // No change to tree as element does not exist
+assert_eq!(recursive_bst.size(), 4);
+
+// View pre-order, in-order and post-order traversals
+assert_eq!(iterative_bst.pre_order_vec(), vec![&15, &5, &2, &25]);
+assert_eq!(iterative_bst.in_order_vec(), vec![&2, &5, &15, &25]);
+assert_eq!(iterative_bst.post_order_vec(), vec![&2, &5, &25, &15]);
+
+assert_eq!(recursive_bst.pre_order_vec(), vec![&15, &5, &2, &25]);
+assert_eq!(recursive_bst.in_order_vec(), vec![&2, &5, &15, &25]);
+assert_eq!(recursive_bst.post_order_vec(), vec![&2, &5, &25, &15]);
+
+// Compare equality of trees
+assert_eq!(iterative_bst.sorted_vec(), recursive_bst.sorted_vec());
+assert_ne!(iterative_bst, IterativeBST::new());
+assert_ne!(recursive_bst, RecursiveBST::new());
+```
+
+## License
 
 [MIT License](LICENSE)
 
+## Contributing
+
+Please read the [CONTRIBUTING.md](CONTRIBUTING.md) before contributing! (Thank you!)
+
 ## Inspiration
 
-The book [Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial.github.io/too-many-lists/) inspired me to try and
-implement a Binary Search Trees within the language. I had also been wanting to create
-my first library for other crates to use.
+The book [Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial.github.io/too-many-lists/) inspired me
+to try and implement a Binary Search Trees within the language. I had also been wanting to create my first library for
+other crates to use.