diff options
| author | bors <bors@rust-lang.org> | 2015-02-07 14:08:38 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-02-07 14:08:38 +0000 |
| commit | 8661b3dc0fbb9e21b94266ba62e23cebb8f0603f (patch) | |
| tree | 7b140bc2081a78ce5de68e6dc57ff3b8ced62fb0 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 80627cd3cc4099b76cb2fb26ebe2f2f8a6c2335e (diff) | |
| parent | 4583272bf5054e84c4c59ba3b9334a52cfcf5208 (diff) | |
| download | rust-8661b3dc0fbb9e21b94266ba62e23cebb8f0603f.tar.gz rust-8661b3dc0fbb9e21b94266ba62e23cebb8f0603f.zip | |
Auto merge of #21971 - pnkfelix:fsk-restrict-fixdsz-array-moves, r=nikomatsakis
Revised version of PR #21930.
Restrictions on moves into and out-from fixed-length arrays.
(There was only one use of this "feature" in the compiler source.)
Note 1: the change to the error message in tests/compile-fail/borrowck-use-in-index-lvalue.rs, where we now report that *w is uninitialized (rather than w), was unintended fallout from the implementation strategy used here. The change appears harmless to me, but I welcome advice on how to bring back the old message, which was slightly cleaner (i.e. less unintelligible) since that the syntactic form *w does not actually appear in the source text.
Note 2: the move out-from restriction to only apply to expr[i], and not destructuring bind (e.g. f([a, b, c]: Array) { ... }) since the latter is compatible with nonzeroing drop, AFAICT.
[breaking-change]
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions