assignment_1

[k2jac9]

What changes are you trying to make?

🔄 Changes Implemented

• Refactoring the code for the "Missing Number in Range" problem to handle edge cases correctly. This includes using the maximum value from the list (instead of its length) to determine the full range of numbers and correctly account for repeated numbers.

What did you learn from the changes you have made?

📚 Key Learnings

• Relying on len(nums) can lead to incorrect results when the missing numbers lie beyond the list length.
• Using max(nums) ensures that the complete expected range of numbers is considered.
• Different approaches (set difference vs. boolean array) have their own trade-offs in terms of readability and space usage.

Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?

🔍 Alternative Approaches Considered

• One alternative was using a boolean (or frequency) array to mark the presence of numbers, then iterating over it to identify which indices (numbers) were not marked.
• Another approach considered was modifying the list in-place using negation to mark visited numbers, but that approach struggled with cases where the expected range extends beyond the list length.

Were there any challenges? If so, what issue(s) did you face? How did you overcome it?

🚧 Challenges & Solutions

• A key challenge was handling cases like [0, 1] and [0] where the missing number is at the end of the expected range. Initially, the code only checked up to len(nums), which was insufficient.
• This was overcome by adjusting the logic to use max(nums) to determine the upper bound of the range, ensuring that all possible missing numbers are considered.

How were these changes tested?

🧪 Testing Methodology

• The code was tested with multiple cases, including:
  • [0, 2] should return [1].
  • [5, 0, 1] should return [2, 3, 4].
  • [0, 1] should return -1 (no missing numbers).
  • [0] should return [1].
• The outputs from these test cases were printed and verified against expected results.

A reference to a related issue in your repository (if applicable)

🔗 N/A

Checklist ✅

• I can confirm that my changes are working as intended