




Sponsored
Sponsored
This approach utilizes dynamic programming to count the number of non-negative integers without consecutive ones. By breaking down the problem, we can avoid redundant work by storing solutions to subproblems.
Time Complexity: O(1) since we iterate over a fixed number of bits (30 bits for int).
Space Complexity: O(1) for storing a constant size dp array.
1using System;
2
3public class Solution {
4    public int FindIntegers(int num) {
5        int[] dp = new int[31];
6        dp[0] = 1;
7        dp[1] = 2;
8        for (int i = 2; i < 31; i++) dp[i] = dp[i - 1] + dp[i - 2];
9
10        int prev_bit = 0, result = 0;
11
12        for (int i = 29; i >= 0; i--) {
13            if ((num & (1 << i)) != 0) {
14                result += dp[i];
15                if (prev_bit == 1) return result;
16                prev_bit = 1;
17            } else {
18                prev_bit = 0;
19            }
20        }
21        return result + 1;
22    }
23
24    public static void Main(string[] args) {
25        Solution sol = new Solution();
26        int n = 5;
27        Console.WriteLine(sol.FindIntegers(n));
28    }
29}The C# variation begins with setting up a dp array representing bit lengths and valid numbers without consecutive ones. As num is assessed bit by bit, the cumulative results are tallied, checking for consecutive 1s to ensure rule adherence.
In this approach, we tackle the problem recursively and use memoization to store and retrieve solutions to subproblems, thereby optimizing overlapping subproblem calculations.
Time Complexity: Generally O(log n), as the recursion iterates over each bit once.
Space Complexity: O(log n) due to the recursive call stack and memo storage.
1class Solution:
2    def __init__(self)
The Python solution mirrors the C++ solution by breaking down the integer into binary bits and evaluating recursively through depth-first search. It stores computed results in a dictionary to avoid re-calculating overlapping subproblems.