cargo rm foo on error should suggest --dev or --build, if appropriate

[epage]

Problem

I just ran

$ cargo rm dunce
    Removing dunce from dependencies
error: the dependency `dunce` could not be found in `dependencies`.

Proposed Solution

It'd be nice if the error had a note saying that a --dev dependency existed

Notes

No response

[calavera]

It'd be nice if the error had a note saying that a --dev dependency existed

If Cargo knows that the development dependency exists, isn't it more user friendly to remove it all together?

[epage]

If you accidentally run cargo rm dunce twice, it shouldn't act as if you did cargo rm --dev dunce.

While "if the tool knew what I intended, it should just do it" is a great principle, I feel like over doing it could lead to some very wrong behavior.

[Rustin170506]

@rustbot claim

[Rustin170506]

I am working on it.