Skip to main content

LeetCode 129 Sum Root to Leaf Number

 

LeetCode 129 Sum Root to Leaf Numbers

Given a root of binary tree containing digits from 0 to 9 only. Return the total sum of all root to leaf.

The question is taken from the book “Elements of Programming Interviews in Python” page 125 https://amzn.to/3y84FHQ

We see we have here these routes to path

  1. 495
  2. +491
  3. +40

Which in total is 1026

Now let’s see how to solve it in java

/**
 * Definition for a binary tree node.
 * public class TreeNode {
 *     int val;
 *     TreeNode left;
 *     TreeNode right;
 *     TreeNode() {}
 *     TreeNode(int val) { this.val = val; }
 *     TreeNode(int val, TreeNode left, TreeNode right) {
 *         this.val = val;
 *         this.left = left;
 *         this.right = right;
 *     }
 * }
 */
class Solution {
    
    // This is an excellent trick to save us from passing params.
    int total = 0;
    
    public int sumNumbers(TreeNode root) {
        sumNumbers(root, 0);
        return total;
    }
    
    private void sumNumbers(TreeNode root, int singlePathSum) {
        
        // Step 1: Identify *no node* if no node given to us do nothing.
        if (root == null) return;
        
        // Step 2: Identify *leaf* node add the leaf node and return total.
        if (root.left == null && root.right == null) {
            total = total + (singlePathSum * 10 + root.val);
            return;
        }
        
        // Step 3: Mid tree - calc right and left.
        sumNumbers(root.left, root.val + singlePathSum * 10);
        sumNumbers(root.right, root.val + singlePathSum * 10);
        
        return;

    } 
}

As we see we have a few steps

  1. First we use a trick to hold on to total in a member variable, this helps it with the recursion.
  2. Step 1 we identify the extreme case of having no real root we do nothing nothing to add here.
  3. Step 2 We identify a leaf node and add it to total and multiply the so far by 10.
  4. Step 3 We identify we are in middle of tree and do the recursion on right and left, we let those recursion steps update the total.

To see the full question go to page 125 on book below which I think is the best book for learning programming interviews

Comments

Popular posts from this blog

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is

Alternatives to Using UUIDs

  Alternatives to Using UUIDs UUIDs are valuable for several reasons: Global Uniqueness : UUIDs are designed to be globally unique across systems, ensuring that no two identifiers collide unintentionally. This property is crucial for distributed systems, databases, and scenarios where data needs to be uniquely identified regardless of location or time. Standardization : UUIDs adhere to well-defined formats (such as UUIDv4) and are widely supported by various programming languages and platforms. This consistency simplifies interoperability and data exchange. High Collision Resistance : The probability of generating duplicate UUIDs is extremely low due to the combination of timestamp, random bits, and other factors. This collision resistance is essential for avoiding data corruption. However, there are situations where UUIDs may not be the optimal choice: Length and Readability : UUIDs are lengthy (typically 36 characters in their canonical form) and may not be human-readable. In URLs,

Bellman Ford Graph Algorithm

The Shortest path algorithms so you go to google maps and you want to find the shortest path from one city to another.  Two algorithms can help you, they both calculate the shortest distance from a source node into all other nodes, one node can handle negative weights with cycles and another cannot, Dijkstra cannot and bellman ford can. One is Dijkstra if you run the Dijkstra algorithm on this map its input would be a single source node and its output would be the path to all other vertices.  However, there is a caveat if Elon mask comes and with some magic creates a black hole loop which makes one of the edges negative weight then the Dijkstra algorithm would fail to give you the answer. This is where bellman Ford algorithm comes into place, it's like the Dijkstra algorithm only it knows to handle well negative weight in edges. Dijkstra has an issue handling negative weights and cycles Bellman's ford algorithm target is to find the shortest path from a single node in a graph t