Issue: After largest key deletion all next/pre queries on t.maxC gives nil pointer
What's Happening:
When a largest node is removed from the tree due to the deletion operation, the tree is correctly updated. However, the t.maxC node still points to the deleted node, causing all queries of Next or Previous from t.maxC to result in a nil pointer.
Scenario: Deletion of the Largest Key
Issue: After largest key deletion all next/pre queries on t.maxC gives nil pointer
What's Happening: When a largest node is removed from the tree due to the deletion operation, the tree is correctly updated. However, the
t.maxC
node still points to the deleted node, causing all queries ofNext
orPrevious
fromt.maxC
to result in a nil pointer.