Feature Request: Don't warn for unused variables in unimplemented!() methods

If you expect to flesh out the unimplemented!() before a major release, then why is it not todo!()? To me unimplemented!() is a long-term placeholder for something that might be added at some point, or not, such as adding floating point to an integer-only micro-computer. I think this post captured the distinction between the two macros quite well.

2 Likes