Todo List OOP Design

Requirements Create a class with the following interface: An external helper, check_todo(id) -> bool, is available in O(1) time. It returns True exactly when the corresponding entry has been marked done. Completion status is managed outside this class; the class itself is responsible only for add, delete, and retrieval operations. Interviewers evaluate the design on these points: add and delete must run in O(1) amortized time. get_todo and get_all must each take O(n) time…