Behnam Esfahbod

I'm sure there are many examples where these can be helpful. Here's one that inspired me to write up this proposal: https://github.com/servo/unicode-bidi/issues/46#issuecomment-316778436 /cc @alexcrichton, @Manishearth, @anowell

Here’s a summary of similar features in some other package managers. ---- ## JS NPM NPM CLI has built-in `outdated` subcommand that shows the status of packages that their *current*,...

In summary: 1. JS and Ruby package managers have built-in `outdated` subcommand to list packages "not in good standing", in the meaning that their installed version is not what's asked...

So, IMHO, we can plan to for these functionalities, applicable only to *direct dependencies* of a package/workspace. a) A built-in `outdated` command to help developers find outdated direct dependencies. This...

Unfortunately, `cargo-outdated` package doesn't have any support for workspaces, yet. Also, a question would be about the original proposal to add *optional* warning (possibly as an opt-in, via env-var and/or...

Good ideas, @Keats! > Having the URL in the output is quite nice to be able to see the changes too. Agreed. Also, on a similar note, a `--verbose` option...

So, looks like we have general consensus on the core functionality of a built-in `outdated` subcommand and the rest can be discussed per PR, I assume. Also, let's CC author...

Agreed, @Keats. :) Funny thing about `build-dependencies`: I could tell what it is, but didn't find it anywhere under the manifest reference: . Turns out, it's only mentioned in this...

@alexcrichton, is this something that needs an RFC, or we can go ahead with the general consensus here and start the implementation? If no RFC, I suppose we can create...

> After removing Cargo.lock: @lnicola, are you saying that `cargo update` doesn't give you the same results? If so, can you be a bit more specific on in which circumstances...