Todo-or-die – Provides procedural macros that act as checked reminders
Reasons not to use something like this:1. Want to run a build from a version from a few months ago, well things are fixed at the head of the main branch, but a todo in the old version are now bad and break the build.  No binary searching for where a bug was introduced, or doing a patch of a previous release.2. Github is down or you don't have internet access, now one of the key strengths of git (distributed, works offline) no longer works.3. You have a large team, now nobody can get any work done for the length of time it takes a single person to fix the problem.4.  Your automatic cut for the weekly release runs at 3am, but a todo expired at midnight.  Now the person in charge of the push to prod needs to do manual work, probably slowing down the cadence of testing the release.5. Rust has bad compile times, this will only make it worse.