about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-12-13 01:53:06 +0000
committerbors <bors@rust-lang.org>2015-12-13 01:53:06 +0000
commit35b6461b6e7419ef5b81d02dfe53172219103764 (patch)
tree95f680e691b393f79d02f822f917ff69d2771ec2 /src/libstd/sys/unix/stack_overflow.rs
parent1ddaf8bdf4ea9b13d2dd96f7a10669dd63da678a (diff)
parent5b9dd6a016adb5ed67e150643fb7e21dcc916845 (diff)
downloadrust-35b6461b6e7419ef5b81d02dfe53172219103764.tar.gz
rust-35b6461b6e7419ef5b81d02dfe53172219103764.zip
Auto merge of #30310 - mbrubeck:doc-vec-bounds, r=steveklabnik
r? @steveklabnik

Currently neither the API docs nor the book clearly explain that out-of-bounds array indexing causes a panic.  Since this is fairly important and seems to surprise a number of new Rust programmers, I think it's worth adding to both places.  (But if you think it would be better to put this info in the API docs only, that's fine too.)

Some specific things I'd like feedback on:

* The new text here talks about panicking, which hasn't been formally introduced at this point in chapter 5 (though it has been mentioned in previous sections too).
* Similarly the `Vec::get` example uses `Option<T>` which hasn't been fully introduced yet.  Should we leave out this example?
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions