TODO items in code are easy to get lost and still be there years later; translating them into issues helps avoid this.
(I am being somewhat hypocritical here, as much of my own code also contains untracked TODOs.)
Translating the current TODO into an issue: checkObservableNotNegative should raise a custom warning rather than a generic one.
TODOitems in code are easy to get lost and still be there years later; translating them into issues helps avoid this.(I am being somewhat hypocritical here, as much of my own code also contains untracked
TODOs.)Translating the current TODO into an issue:
checkObservableNotNegativeshould raise a custom warning rather than a generic one.