Ignacio Corderi

This is still broken, can we ask for a hand on rust-weekly for a volunteer to fix it?

I would argue that rust `()` always maps to python `None`. In the context of calling a python method, the signature should be something like this instead: ```rust fn call_method(&self,...

Cool, that's great! By the way, don't the _cargo_ subcommands crates "need" (or expect) to be named `cargo-xyz`?

I think the need to generalized something like is there. It's a very common case to have a binary on which you can call a number of sub-commands. Take [cargo](https://github.com/rust-lang/cargo/blob/master/src/bin/cargo.rs)...

I think that [example](https://github.com/docopt/docopt.rs/blob/master/examples/cargo.rs) helps a lot, thanks. How would you get the args for each command in there? Does this work? ``` rust #[deriving(Decodable, Show)] enum Command { Build...

Seems we can agree on what the use case looks like. Questions now is how we want to surface that to the library user... I think if we can find...

@BurntSushi I totally understand the priorities. Without macros is gonna be a tough one. > If there's another approach that doesn't involved syntax extensions, then maybe I'll pursue that. But...

@BurntSushi and for those following up on this. I've been playing with the idea and I've got some pieces of it working. - You can find some initial `Command` and...

@keleshev that's python :D Function decorators are slightly more straightforward than messing with the AST with procedural macros in Rust.

I run into this same bug but described it at #158. The `Cargo.toml` associated with a given `*.rs` should be the first `Cargo.toml` from that file up, **NOT** from the...