Serialize and Deserialize Binary Tree in DSA C - Time & Space Complexity

Time Complexity: Serialize and Deserialize Binary Tree

O(n)

Understanding Time Complexity

We want to understand how long it takes to convert a binary tree into a string and back.

How does the time needed grow as the tree gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Serialize: convert tree to string
void serialize(TreeNode* root, FILE* out) {
    if (root == NULL) {
        fprintf(out, "# ");
        return;
    }
    fprintf(out, "%d ", root->val);
    serialize(root->left, out);
    serialize(root->right, out);
}

// Deserialize: convert string back to tree
TreeNode* deserialize(FILE* in) {
    char val[10];
    if (!fscanf(in, "%s", val) || strcmp(val, "#") == 0) return NULL;
    TreeNode* node = (TreeNode*)malloc(sizeof(TreeNode));
    node->val = atoi(val);
    node->left = deserialize(in);
    node->right = deserialize(in);
    return node;
}
    

This code saves a binary tree to a string using preorder traversal and rebuilds it from that string.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Recursive calls visiting each node once.
• How many times: Exactly once per node in the tree.

How Execution Grows With Input

Each node is visited once during serialization and once during deserialization.

Input Size (n)	Approx. Operations
10	About 20 (10 nodes serialize + 10 nodes deserialize)
100	About 200
1000	About 2000

Pattern observation: Operations grow roughly twice the number of nodes, so growth is linear.

Final Time Complexity

Time Complexity: O(n)

This means the time to serialize and deserialize grows directly with the number of nodes in the tree.

Common Mistake

[X] Wrong: "Serialization takes constant time because it just writes a string."

[OK] Correct: The string length depends on the number of nodes, so the process must visit each node, making time grow with tree size.

Interview Connect

Understanding this helps you explain how tree data can be saved and restored efficiently, a common skill in many coding tasks.

Self-Check

"What if we used level-order traversal instead of preorder for serialization? How would the time complexity change?"

Practice

1. What is the main purpose of serialize and deserialize functions in the context of a binary tree?

easy

A. Delete all nodes in the binary tree

B. Sort the binary tree nodes in ascending order

C. Find the height of the binary tree

D. Convert a binary tree to a string and back to a binary tree

Solution

1. Step 1: Understand serialization

   Serialization means converting a binary tree into a string format so it can be stored or sent easily.

2. Step 2: Understand deserialization

   Deserialization means converting the string back into the original binary tree structure.

3. Final Answer:

   Convert a binary tree to a string and back to a binary tree -> Option D

4. Quick Check:

   Serialize + Deserialize = Convert tree to string and back [OK]

Hint: Serialization means tree to string, deserialization reverses it [OK]

Common Mistakes:

• Thinking serialization sorts nodes
• Confusing serialization with deletion
• Believing serialization finds tree height

2. Which of the following is the correct way to represent a null node during serialization of a binary tree in C?

easy

A. "null"

B. "#"

C. "0"

D. "-1"

Solution

1. Step 1: Identify common null markers

   In many serialization methods, a special symbol like "#" is used to mark null nodes to distinguish them from valid values.

2. Step 2: Compare options

   "null" is a string but longer; "0" and "-1" can be valid node values, so "#" is safest and most common.

3. Final Answer:

   "#" -> Option B

4. Quick Check:

   Null node marker = "#" [OK]

Hint: Use '#' to mark null nodes in serialization [OK]

Common Mistakes:

• Using '0' which can be a valid node value
• Using 'null' string which is verbose
• Using '-1' which might be a valid value

3. Given the following serialized string of a binary tree using preorder traversal: "1,2,#,#,3,4,#,#,5,#,#", what is the inorder traversal of the tree?

medium

A. 1 2 3 4 5

B. 2 4 1 3 5

C. 2 1 4 3 5

D. 4 2 5 3 1

Solution

1. Step 1: Reconstruct the tree from preorder

   Preorder: root, left, right. The string means:
   Root=1
   Left subtree: 2, #, # (2 with no children)
   Right subtree: 3,4,#,#,5,#,# (3 with left=4 no children, right=5 no children)

2. Step 2: Find inorder traversal

   Inorder: left, root, right
   Left subtree inorder: 2
   Root: 1
   Right subtree inorder: left(4), root(3), right(5) -> 4 3 5
   Combine: 2 1 4 3 5

3. Final Answer:

   2 1 4 3 5 -> Option C

4. Quick Check:

   Preorder to inorder conversion = 2 1 4 3 5 [OK]

Hint: Rebuild tree from preorder, then do inorder traversal [OK]

Common Mistakes:

• Mixing preorder and inorder orders
• Ignoring null markers and misbuilding tree
• Swapping left and right children

4. Consider this buggy C code snippet for deserializing a binary tree node from a string token:

if (strcmp(token, "#") == 0) {
    return NULL;
}
node = malloc(sizeof(TreeNode));
node->val = atoi(token);
node->left = deserialize(tokens);
node->right = deserialize(tokens);
return node;

What is the main issue causing incorrect deserialization?

medium

A. Not advancing the token pointer before recursive calls

B. Using atoi instead of strtol for conversion

C. Not checking if malloc returns NULL

D. Comparing token with "#" incorrectly

Solution

1. Step 1: Understand token usage

   Deserialization uses tokens from a list or array. Each recursive call must move to the next token to read the next node.

2. Step 2: Identify missing token advancement

   The code does not advance the token pointer before calling deserialize recursively, so it reads the same token repeatedly causing infinite recursion or wrong tree.

3. Final Answer:

   Not advancing the token pointer before recursive calls -> Option A

4. Quick Check:

   Advance token pointer before recursion [OK]

Hint: Always move to next token before recursive deserialize calls [OK]

Common Mistakes:

• Ignoring token pointer movement
• Focusing on atoi vs strtol which is less critical here
• Missing malloc NULL check but not main bug

5. You want to serialize a binary tree and then deserialize it back. Which approach ensures the tree structure is preserved even if node values contain commas or special characters?

hard

A. Use level-order traversal with a delimiter and escape special characters in node values

B. Use preorder traversal with commas and '#' for nulls without escaping

C. Serialize only node values ignoring nulls

D. Store tree as an array without any delimiter

Solution

1. Step 1: Understand problem with special characters

   If node values contain commas or special symbols, simple comma separation breaks parsing because commas appear inside values.

2. Step 2: Use level-order with escaping

   Level-order traversal with a delimiter and escaping special characters ensures each node value is correctly separated and nulls are marked, preserving structure.

3. Step 3: Why other options fail

   Use preorder traversal with commas and '#' for nulls without escaping fails because no escaping means parsing errors. Serialize only node values ignoring nulls loses structure by ignoring nulls. Store tree as an array without any delimiter without delimiter cannot separate nodes.

4. Final Answer:

   Use level-order traversal with a delimiter and escape special characters in node values -> Option A

5. Quick Check:

   Escape special chars + delimiter + level-order = safe serialization [OK]

Hint: Escape special chars and use delimiter in level-order serialization [OK]

Common Mistakes:

• Ignoring special characters in node values
• Not escaping delimiters causing parse errors
• Skipping null nodes losing tree shape