Open
Description
Problem
currently, cargo init some_project --lib --bin
provides the following output:
error: can't specify both lib and binary outputs
Proposed Solution
have a third built in package template that takes a library-first approach
Notes
It seems there is a use-case for projects that are both a library and a binary. clone and compile: its a binary. add to your cargo manifest: it's a library. It also seems there is a right and wrong way to do it.
I think it would be useful to have a package template for library-first applications