Binary Search Trees (BST) seem to be a hot topic in technical interviews.
So, in order to help me prepare for all these grilling technical tests, I thought I’d give it a crack at implementing insertion, deletion and verification logic since I’ve already done both breath-first and depth-first traversals.
Starting with something nice and easy, here’s a function that checks whether a given Tree is a BST. For instance, the following is not a BST as 5 is on the right side of 20 but is less than 20.
20 / \ 10 30 / \ 5 40
Here, we start with unbounded lower and upper limits (represented by None) at the root element.
Using the earlier tree as example, as we traverse down the right branch of 20, the nodes must be > 20, therefore the lower bound is now Some 20. Nodes on the left branch of 30 is also subject to an upper bound of Some 30, nodes on the right branch of 30 will have a higher lower bound (now Some 30).
And so on.
To insert a new node we need to traverse down the tree, turning left or right depending on whether the newValue is < or > the value of the current node. We repeat this until we either find an empty spot to insert a new node or we find a node with matching value (in which case there’s no change to the tree).
We have left the hardest for last.
The delete function starts with a similar traversal logic as insert, and where the value is:
- not found, then do nothing
- only has left child, then replace node with left child
- only has right child, then replace node with right child
It gets complicated when the node has both children, and those children have their own children. At that point, you find the in-order predecessor (the right-most leaf of the left branch), replace the current node’s value with its in-order predecessor, and delete the predecessor.
To walk through it with an example, suppose we have the following tree
7 / \ 3 9 / \ / \ 2 5 8 10 / \ 4 6
Suppose we want to delete 7, its in-order predecessor is 6.
We will delete 6 from the left branch.
7 / \ 3 9 / \ / \ 2 5 8 10 / 4
and then substitute the root’s (remember, the node to be delete) value to 6.
6 / \ 3 9 / \ / \ 2 5 8 10 / 4
And now we can translate this into code.
I think looking back, the match..with clause is a bit verbose but also helps make those different cases very clear. Whilst I can perhaps implement it with fewer lines of code, I think the explicitness is a win over clever code that’s hard-to-understand.
- Wikipedia entry
- Breath-First Traversal
- Depth-First Traversal
- All my Project Euler solutions in F#
- All my Advent of Code solutions in F#
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong