3 ms·

For 1-2, the todo panic stacktrace should tell you exactly what went wrong. For 3-4 you can set TODO_OR_DIE_SKIP, as documented for the crate, to disable all t

by zaarn 5y ago

For 1-2, the todo panic stacktrace should tell you exactly what went wrong. For 3-4 you can set TODO_OR_DIE_SKIP, as documented for the crate, to disable all the todo checks at compile time. 5 is getting better over time.

DuskStar 5y ago
And now TODO_OR_DIE_SKIP is set in prod and will never be disabled.
- zaarn 5y ago
  If it worked before the date, it'll keep working after unless there was some other reason for it to be added (an API shutdown deadline for example) which prevents it from working anyway.