Chapters

Hide chapters

Data Structures & Algorithms in Swift

Fifth Edition · iOS 18 · Swift 6.0 · Xcode 16.2

14. Binary Search Trees
Written by Kelvin Lau

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

A binary search tree, or BST, is a data structure that facilitates fast lookup, insert and removal operations. Consider the following decision tree where picking a side forfeits all the possibilities of the other side, cutting the problem in half.

no yes no yes no yes no yes yes no Should I go the gym? Did I go yesterday? Did I go jogging yesterday? Am I still feeling sore? Did I run 5km? Go to the gym Go to the gym Go to sleep Rest for the day Break Go to the gym Did you slack off in the last session?

Once you make a decision and choose a branch, there is no looking back. You keep going until you make a final decision at a leaf node. Binary trees let you do the same thing. Specifically, a binary search tree imposes two rules on the binary tree you saw in the previous chapter:

  • The value of a left child must be less than the value of its parent.
  • Consequently, the value of a right child must be greater than or equal to the value of its parent.

Binary search trees use this property to save you from performing unnecessary checking. As a result, lookup, insert and removal have an average time complexity of O(log n), which is considerably faster than linear data structures such as arrays and linked lists.

In this chapter, you’ll learn about the benefits of the BST relative to an array and, as usual, implement the data structure from scratch.

Case study: array vs. BST

To illustrate the power of using a BST, you’ll look at some common operations and compare the performance of arrays against the binary search tree.

Consider the following two collections:

1 25 88 18 45 4 40 105 20 77 70 40 18 77 1 20 70 105 4 25 45 88

Lookup

There’s only one way to do element lookups for an unsorted array. You need to check every element in the array from the start:

0 49 35 56 54 1 01 222 56 04 13
Loucyvupx his 630

00 90 18 90 980 02 78 9 07 6 75
Giultqojy piw 678

Insertion

The performance benefits for the insertion operation follow a similar story. Assume you want to insert 0 into a collection:

3 61 31 07 21 4 55 426 62 58 60 0 2 78 96 46 51 6 60 683 29 45 30
Idlithixx 1 oy jutyif uzsic

23 30 61 39 398 78 25 8 68 9 67

Removal

Similar to insertion, removing an element in an array also triggers a shuffling of elements:

1 21 34 77 69 3 14 711 67 13 45 5 65 15 68 8 40 549 13 77 57 mudabi 27
Jewifobw 92 qgis hro aykuh

63 07 11 58 092 93 90 6 26 1 02

Implementation

Open up the starter project for this chapter. In it, you’ll find the BinaryNode type that you created in the previous chapter. Create a new file named BinarySearchTree.swift and add the following inside the file:

Inserting elements

Per the rules of the BST, nodes of the left child must contain values less than the current node. Nodes of the right child must contain values greater than or equal to the current node. You’ll implement the insert method while respecting these rules.

5 7 9 1 0 6 2 3 0 1 nofuqnel ogcizulweb

1 1 0 9 5 0 6 0 9 9 okjaratjag kaposluc 3 6 7

Finding elements

Finding an element in a BST requires you to traverse through its nodes. It’s possible to come up with a relatively simple implementation by using the existing traversal mechanisms that you learned about in the previous chapter.

Optimizing contains

You can rely on the rules of the BST to avoid needless comparisons. Back in BinarySearchTree.swift, update the contains method to the following:

Removing elements

Removing elements is a little more tricky, as you need to handle a few different scenarios.

Case 1: Leaf node

Removing a leaf node is straightforward; simply detach the leaf node.

2 7 3 1 6 6
Qinofihw 0

Case 2: Nodes with one child

When removing nodes with one child, you’ll need to reconnect that one child with the rest of the tree:

6 6 8 4 4 9
Bodesewf 4, zfutq rop 3 jkimd

Case 3: Nodes with two children

Nodes with two children are a bit more complicated, so a more complex example tree will better illustrate how to handle this situation. Assume that you have the following tree and that you want to remove the value 25:

60 Qevijo 34 04 87 42 50 52 38 49 75 16 80 60 58

55 54 04 15 38 01 29 83 23 39 07 01

34 Pegvujav cekie 38 56 49 61 81 29 51 85 53 25 40 47

06 22 41 87 69 84 42 47 66 40 00 29 34

Implementation

Open up BinarySearchTree.swift to implement remove. Add the following code at the bottom of the file:

Key points

  • The binary search tree is a powerful data structure for holding sorted data.
  • Elements of the binary search tree must be comparable. You can achieve this using a generic constraint or by supplying closures to perform the comparison.
  • The time complexity for insert, remove and contains methods in a BST is O(log n).
  • Performance will degrade to O(n) as the tree becomes unbalanced. This is undesirable, so you’ll learn about a self-balancing binary search tree called the AVL tree in Chapter 16.
Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2026 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now