Nick Cameron

I also want to think about what PingCAP get out of the course: name recognition, a wider pool of applicants, better trained employees/interns, more/better contributors, more clients, downstream users, etc.?

To iterate on > To train folks who already know how to program how to get into Rust and help them into building distributed systems with it. Teach them the...

A lightweight way to help here might be to just ignore nested virtual manifests. If we want to be strict, we could do this only if the outer manifest includes...

I don't think the exclude trick quite works for the case I have in mind. I have: ``` . ├── Cargo.toml ├── bar │   ├── Cargo.toml │   └── baz │  ...

> Why does bar/baz needs to be a member of the outer workspace though? Can it be a regular path dependency? It's not a dependency of anything in the `.`...

I discussed with @alexcrichton on irc, it turns out that this would actually be a breaking change: in my example above, you can't currently build the outer workspace but you...

@alexcrichton how would we run rustfmt tests if we used it as a dep? @wycats the motivation is where you want to pull in a workspace project as a Git...

I don't see much of a use case - you can just do `cargo build` and ignore the output for the last crate. If you really need to do this...

Implement an `Executor`. That lets you intercept every call to rustc and you can do nothing if it is the last crate.

Docs are a little thin, but start here: https://github.com/rust-lang/cargo/blob/609371f0b4d862a94e2e3b8e4e8c2a4a2fc7e2e7/src/cargo/ops/cargo_rustc/mod.rs#L62-L64 You can look at the RLS for an example of how to use them: https://github.com/rust-lang-nursery/rls/blob/master/src/build.rs#L288