The todo! macro causes a `not yet implemented` panic message?

[beyarkay]

Not sure if this is the correct place for this question, but what is the reasoning behind the todo! docs making the difference between todo! and unimplemented!, but then the todo! macro results in an error like:

thread 'main' panicked at 'not yet implemented', ...

It seems really counter intuitive to me. Is there a reason why the panic message is not:

thread 'main' panicked at 'still to do', ...

or a different panic message that's without a doubt not related to the unimplemented macro? (for consistency with how much the docs stress the difference between them)

For reference, here's the paragraph for the difference between unimplemented! and todo!:

The difference between unimplemented! and todo! is that while todo! conveys an intent of implementing the functionality later and the message is “not yet implemented”, unimplemented! makes no such claims. Its message is “not implemented”. Also some IDEs will mark todo!s.

"Not yet implemented" implies the same message as "still to do"? IMO

[jyn514]

I'm going to close this as not a bug, the current error and documentation seem fine to me.