Oh wow, this is a really bad thing and I had never run into it before, but I completely understand your point. I definitely think we should do this.

@searls Thanks for your quick response! Now that we know what we're looking for, we can make sure not to do a multiple replace()s on the same function any more. But for others, it might make sense to communicate that this can cause issues. 😄

Instead of a warning, as the title suggests, I think it would be better to allow replacing the same method twice but still support reseting to the original method.

I am struggling to imagine why someone would want to reset the same method twice. If there's a case for that, I feel like that a more narrowly td.func-scoped reset would probably be a better fit.

In fact, as I've thought more about this, I feel like an error (as opposed to a warning) would be more appropriate, since the behavior folks will experience will be confusing at best and undefined at worst.

We ran into this as well. It would be nice if td.replace would throw an error if the function was already stubbed.