]> git.proxmox.com Git - cargo.git/commit
Add unstable documentation.
authorEric Huss <eric@huss.org>
Sat, 7 Apr 2018 21:11:07 +0000 (14:11 -0700)
committerEric Huss <eric@huss.org>
Sun, 8 Apr 2018 17:48:52 +0000 (10:48 -0700)
commit740525f2c4fc1106120692cde51c7d29c79ca6f0
treeefb91c5151c7366d63d1aac737fd256ecef6c74d
parent8aa2794a654f5ded327df28747e98ba2e152ea75
Add unstable documentation.

I kept most of these relatively brief with the intent that more complete
documentation would be added when a feature is stabilized.  I did my best to be
accurate, but I am unfamiliar with most of these features, so please let me know
if anything should change.

@matklad: I didn't fully understand the use case for `minimal-versions`, so I
didn't say much about it.  In particular, I didn't understand why one wouldn't
just use `~` or `=` semver requirements if you wanted to be careful about not
pulling in a newer version.  When someone says "1.0", aren't they explicitly
saying they want a newer version (up to 2.0) if it's available?  The example
in the RFC of switching a dependency to "=1.0" sounds like a breaking change
(essentially downgrading a dependency).
src/cargo/core/features.rs
src/doc/src/SUMMARY.md
src/doc/src/reference/index.md
src/doc/src/reference/unstable.md [new file with mode: 0644]