diff options
| author | bors <bors@rust-lang.org> | 2014-06-04 18:56:48 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-06-04 18:56:48 -0700 |
| commit | 193574ae1e3881f95afb8b3e385a9e410ac6798a (patch) | |
| tree | 169d7f666b23207484a732ff533715b2ca16535e /src/test/codegen/stack-alloc-string-slice.cc | |
| parent | aa09561bb606bb622136ac9ad3702ab1179db5b2 (diff) | |
| parent | 9b228f8424d207fc412bf549d3d9dc8262415f27 (diff) | |
| download | rust-193574ae1e3881f95afb8b3e385a9e410ac6798a.tar.gz rust-193574ae1e3881f95afb8b3e385a9e410ac6798a.zip | |
auto merge of #14529 : brson/rust/ptr, r=brson
This time we're not promoting anything directly to 'stable', but instead promoting functions we're happy with to 'unstable'. They'll become stable in another pass later. * null and mut_null are unstable. Their names may change if the unsafe pointer types change. * copy_memory and copy_overlapping_memory are unstable. We think they aren't going to change. * set_memory and zero_memory are experimental. Both the names and the semantics are under question. * swap and replace are unstable and probably won't change. * read is unstable, probably won't change * read_and_zero is experimental. It's necessity is in doubt. * mem::overwrite is now called ptr::write to match read and is unstable. mem::overwrite is now deprecated * array_each, array_each_with_len, buf_len, and position are all deprecated because they use old style iteration and their utility is generally under question. Note that `mem::overwrite`, which was just declared stable last week, is deprecated now in favor of `ptr::write`. Woo!
Diffstat (limited to 'src/test/codegen/stack-alloc-string-slice.cc')
0 files changed, 0 insertions, 0 deletions
