about summary refs log tree commit diff
path: root/src/test/incremental/thinlto
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2016-12-24 14:29:21 -0500
committerGitHub <noreply@github.com>2016-12-24 14:29:21 -0500
commitd15a47749a7ee1f8bdeb4303e906b4f4bb3d6b81 (patch)
treef46aa37e07afa1de208276761ea9d5599fc4d434 /src/test/incremental/thinlto
parent685027a23e42d272bef63e30848703b9d52e7dfd (diff)
parent71de148649bd9d2548b55e5d52bd0c8b38ffec44 (diff)
downloadrust-d15a47749a7ee1f8bdeb4303e906b4f4bb3d6b81.tar.gz
rust-d15a47749a7ee1f8bdeb4303e906b4f4bb3d6b81.zip
Rollup merge of #38297 - matklad:linked-lists-are-not-cool, r=GuillaumeGomez
Advertise Vec in LinkedList docs

r? @steveklabnik

Hi! We already [advise](https://doc.rust-lang.org/std/collections/#use-a-linkedlist-when) to use `Vec` instead of `LinkedList` in the top-level collections documentation. But I think it may be missed by someone who just directly finds `LinkedList`.

What do you feel about advertising `Vec` directly in `LinkedList` docs as well?
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions