4 ms·
Title is a little click-baity but I fully agree with the sentiment. Just minutes ago I had this experience where a #TODO marked out some extremely rare edge cas
by indoordin0saur 1y ago
Title is a little click-baity but I fully agree with the sentiment. Just minutes ago I had this experience where a #TODO marked out some extremely rare edge case to handle but one that I have never seen actually occur in the 2 years since I put it in there. Still it will be useful to others (and future me) when I look back at the code and wonder why something wasn't handled.
I also agree with users that sometimes these should just be comments. Really depends on your environment and since I work on a team of 2 who maintain my portion of the codebase I stick with using TODOs in this way (seomtimes).
- MathMonkeyMan 1y agoI was on a team that used `// TBD: [...]` for this purpose, so that the "TODO people" wouldn't notice.
- CRConrad 1y agoAdd to that: // PBD: Possibly be done...? // NBD: Not being done! And, Idunno, perhaps some more.