How many subcommands do we want for Cargo? Should this be a first-class thing?
Were any opinions voiced in answer to this question?
re cargo check - I want to see this, I think it's another arrow in the reply to our long compile-times complaint, so I'd like it to be first class in Cargo.
To answer the general question, I think we should expect Cargo to expand the number of sub-commands offered - it's the best way to ensure we have an easy to-use system of core tools. A Rust new-comer should just be able to download Cargo and have access to the standard suite of tools. They shouldn't have to follow a recipe on a web page to download a bunch of stuff and run a bunch of commands in order to get a standard environment - that is the C/C++ world which we are trying to get away from.
The downside is that this means we need to document better, and --help probably has to tier the sub-commands rather than just give a list, but I believe this is a solvable problem.
red flag on aster (wycats)
details please! Can we discuss this at the lang team meeting, whatever it is?
- cargo check (wycats)
- patterns (nmatsakis) How to handle pattern matching on constants - #16 by ahmedcharles
- std::time (wycats) Improvements to the Time APIs by wycats · Pull Request #1288 · rust-lang/rfcs · GitHub
- ffi complaint
- red flag on aster (wycats)
I'd like to remind the core team that we have sub-teams where some of these might be better (or at least primarily) discussed