Why Morris Traversal Inorder Without Stack in DSA Javascript?

The Big Idea

What if you could walk through a tree without carrying any extra baggage or losing your way?

The Scenario

Imagine you have a big family tree drawn on paper, and you want to visit every family member in order. You try to remember where you left off by writing notes or using bookmarks, but it gets messy and confusing.

The Problem

Using extra notes or bookmarks (like a stack) to remember where you are slows you down and can make you lose track. It also uses extra space, which is like carrying a heavy backpack while walking through the tree.

The Solution

Morris Traversal lets you visit every family member in order without carrying any extra notes or bookmarks. It cleverly changes the tree paths temporarily to remember where to go next, then fixes the tree back to normal.

Before vs After

✗ Before

function inorderTraversal(root) {
  let stack = [];
  let current = root;
  while (current || stack.length) {
    while (current) {
      stack.push(current);
      current = current.left;
    }
    current = stack.pop();
    console.log(current.val);
    current = current.right;
  }
}

✓ After

function morrisInorderTraversal(root) {
  let current = root;
  while (current) {
    if (!current.left) {
      console.log(current.val);
      current = current.right;
    } else {
      let predecessor = current.left;
      while (predecessor.right && predecessor.right !== current) {
        predecessor = predecessor.right;
      }
      if (!predecessor.right) {
        predecessor.right = current;
        current = current.left;
      } else {
        predecessor.right = null;
        console.log(current.val);
        current = current.right;
      }
    }
  }
}

What It Enables

You can traverse a binary tree in order using only the tree itself, saving memory and making your code faster and cleaner.

Real Life Example

When working with huge trees in limited memory devices, like embedded systems or mobile apps, Morris Traversal helps you process data without extra memory overhead.

Key Takeaways

Morris Traversal visits nodes without extra memory like stacks or recursion.

It temporarily changes tree links to remember paths, then restores them.

This method is efficient for memory-limited environments.

Practice

1. What is the main advantage of Morris Traversal for inorder tree traversal compared to traditional methods?

easy

A. It only works on binary search trees

B. It is faster than all other traversal methods

C. It requires a queue to store nodes

D. It uses no extra space like stack or recursion

Solution

1. Step 1: Understand Morris Traversal space usage

   Morris Traversal modifies tree links temporarily to avoid using stack or recursion, so it uses O(1) extra space.

2. Step 2: Compare with traditional methods

   Traditional inorder traversal uses stack or recursion which requires O(h) space, where h is tree height.

3. Final Answer:

   It uses no extra space like stack or recursion -> Option D

4. Quick Check:

   Morris Traversal = O(1) space [OK]

Hint: Morris Traversal avoids stack and recursion for space savings [OK]

Common Mistakes:

• Thinking Morris Traversal is faster in time complexity
• Assuming it only works on binary search trees
• Believing it uses extra data structures like queues

2. Which of the following is the correct way to find the inorder predecessor of a node curr in Morris Traversal?

easy

A. Move to the left child of curr and then keep moving right until right child is null or curr

B. Move to the right child of curr until null

C. Move to the left child of curr only once

D. Move to the right child of curr and then keep moving left until left child is null

Solution

1. Step 1: Identify inorder predecessor in Morris Traversal

   The inorder predecessor is the rightmost node in the left subtree of curr.

2. Step 2: Traverse left subtree then rightmost path

   Start at curr.left, move right repeatedly until right child is null or points back to curr.

3. Final Answer:

   Move to the left child of curr and then keep moving right until right child is null or curr -> Option A

4. Quick Check:

   Inorder predecessor = left subtree's rightmost node [OK]

Hint: Inorder predecessor = left child then rightmost path [OK]

Common Mistakes:

• Moving right child first instead of left
• Stopping after one left move without going right
• Confusing predecessor with successor

3. What will be the output of Morris inorder traversal on the following binary tree?

    2
   / \
  1   3

Assuming the traversal prints node values in order.

medium

A. [1, 3, 2]

B. [2, 1, 3]

C. [1, 2, 3]

D. [3, 2, 1]

Solution

1. Step 1: Understand inorder traversal order

   Inorder traversal visits left subtree, then current node, then right subtree.

2. Step 2: Apply Morris traversal on given tree

   Left child is 1, root is 2, right child is 3, so output is [1, 2, 3].

3. Final Answer:

   [1, 2, 3] -> Option C

4. Quick Check:

   Inorder = left, root, right = [1, 2, 3] [OK]

Hint: Inorder prints left, root, right nodes [OK]

Common Mistakes:

• Confusing preorder or postorder with inorder
• Mixing node visit order
• Assuming traversal prints in reverse

4. Consider this snippet of Morris Traversal code:

while (curr !== null) {
  if (curr.left === null) {
    console.log(curr.val);
    curr = curr.right;
  } else {
    let pred = curr.left;
    while (pred.right !== null && pred.right !== curr) {
      pred = pred.right;
    }
    if (pred.right === null) {
      pred.right = curr;
      curr = curr.left;
    } else {
      pred.right = null;
      console.log(curr.val);
      curr = curr.right;
    }
  }
}

What is the error in this code?

medium

A. It misses printing the current node after restoring links

B. It never prints the current node's value

C. It creates infinite loop by not updating curr

D. It incorrectly sets pred.right to curr.left

Solution

1. Step 1: Check when node values are printed

   Values are printed only when curr.left === null, but after restoring links, printing is missing.

2. Step 2: Identify missing print after restoring links

   After setting pred.right = null, the code moves curr = curr.right without printing curr.val.

3. Final Answer:

   It misses printing the current node after restoring links -> Option A

4. Quick Check:

   Print missing after restoring links = bug [OK]

Hint: Print node after restoring links to avoid missing values [OK]

Common Mistakes:

• Not printing node after restoring predecessor link
• Confusing when to update curr pointer
• Incorrectly modifying tree structure

5. You want to modify Morris Traversal inorder to collect node values in an array instead of printing. Which change is necessary to correctly collect all nodes in order?

hard

A. Push curr.val only when curr.left === null

B. Push curr.val both when curr.left === null and after restoring links

C. Push curr.val only after restoring links

D. Push curr.val before moving to left child

Solution

1. Step 1: Identify when nodes are visited in Morris Traversal

   Nodes are visited either when curr.left === null or after restoring the threaded link.

2. Step 2: Collect values at both visit points

   To collect all nodes in inorder, push curr.val both when curr.left === null and after restoring links (before moving right).

3. Final Answer:

   Push curr.val both when curr.left === null and after restoring links -> Option B

4. Quick Check:

   Collect values at both visits = correct inorder [OK]

Hint: Collect node values at both visits for full inorder [OK]

Common Mistakes:

• Collecting values only once misses nodes
• Collecting before moving left causes wrong order
• Ignoring second visit after restoring links