Overflow in intermediate arithmetic
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.
Build confidence with an intuition-first walkthrough focused on math fundamentals.
You are given a string num, representing a large integer. Return the largest-valued odd integer (as a string) that is a non-empty substring of num, or an empty string "" if no odd integer exists.
A substring is a contiguous sequence of characters within a string.
Example 1:
Input: num = "52" Output: "5" Explanation: The only non-empty substrings are "5", "2", and "52". "5" is the only odd number.
Example 2:
Input: num = "4206" Output: "" Explanation: There are no odd numbers in "4206".
Example 3:
Input: num = "35427" Output: "35427" Explanation: "35427" is already an odd number.
Constraints:
1 <= num.length <= 105num only consists of digits and does not contain any leading zeros.Problem summary: You are given a string num, representing a large integer. Return the largest-valued odd integer (as a string) that is a non-empty substring of num, or an empty string "" if no odd integer exists. A substring is a contiguous sequence of characters within a string.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Math · Greedy
"52"
"4206"
"35427"
largest-3-same-digit-number-in-string)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1903: Largest Odd Number in String
class Solution {
public String largestOddNumber(String num) {
for (int i = num.length() - 1; i >= 0; --i) {
int c = num.charAt(i) - '0';
if ((c & 1) == 1) {
return num.substring(0, i + 1);
}
}
return "";
}
}
// Accepted solution for LeetCode #1903: Largest Odd Number in String
func largestOddNumber(num string) string {
for i := len(num) - 1; i >= 0; i-- {
c := num[i] - '0'
if (c & 1) == 1 {
return num[:i+1]
}
}
return ""
}
# Accepted solution for LeetCode #1903: Largest Odd Number in String
class Solution:
def largestOddNumber(self, num: str) -> str:
for i in range(len(num) - 1, -1, -1):
if (int(num[i]) & 1) == 1:
return num[: i + 1]
return ''
// Accepted solution for LeetCode #1903: Largest Odd Number in String
struct Solution;
impl Solution {
fn largest_odd_number(num: String) -> String {
let n = num.len();
let s: Vec<char> = num.chars().collect();
for i in (0..n).rev() {
if (s[i] as u8 - b'0') % 2 == 1 {
return s[0..=i].iter().collect();
}
}
"".to_string()
}
}
#[test]
fn test() {
let num = "52".to_string();
let res = "5".to_string();
assert_eq!(Solution::largest_odd_number(num), res);
let num = "4206".to_string();
let res = "".to_string();
assert_eq!(Solution::largest_odd_number(num), res);
let num = "35427".to_string();
let res = "35427".to_string();
assert_eq!(Solution::largest_odd_number(num), res);
}
// Accepted solution for LeetCode #1903: Largest Odd Number in String
function largestOddNumber(num: string): string {
for (let i = num.length - 1; ~i; --i) {
if (Number(num[i]) & 1) {
return num.slice(0, i + 1);
}
}
return '';
}
Use this to step through a reusable interview workflow for this problem.
Try every possible combination of choices. With n items each having two states (include/exclude), the search space is 2ⁿ. Evaluating each combination takes O(n), giving O(n × 2ⁿ). The recursion stack or subset storage uses O(n) space.
Greedy algorithms typically sort the input (O(n log n)) then make a single pass (O(n)). The sort dominates. If the input is already sorted or the greedy choice can be computed without sorting, time drops to O(n). Proving greedy correctness (exchange argument) is harder than the implementation.
Review these before coding to avoid predictable interview regressions.
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.
Wrong move: Locally optimal choices may fail globally.
Usually fails on: Counterexamples appear on crafted input orderings.
Fix: Verify with exchange argument or monotonic objective before committing.