Support for 'cargo init --force' that overwrites existing files

[sbuller]

Every time I run cargo init I forget the --bin option. I'd prefer an alternative to rm -rf *; cargo init --bin. Alternatively, a n00b mode might be helpful. I'd appreciate it if a bare cargo init stopped to ask me if I'd forgotten the --bin like a n00b again.

[epage]

--bin is now the default but the point still stands ;)

The differences between bins and libs shrunk a little in that we make the Cargo.lock the same.

Deciding what to overwrite with a --force seems dubious. I think I'd prefer to explore cargo init being additive.

[weihanglo]

As of now, cargo init doesn't really generate many files. I doubt it worth making it additive. That said, when cargo gets cargo-template support (#5151), this might be quite interesting to explore.

[epage]

@weihanglo are you then leaning towards "close"? If so, I think thats fine as well.

[weihanglo]

Yes. I am going propose to close this to the cargo team. This looks a feature likely to be an extension of cargo-template.

[epage]

I second.