diff options
| author | bors <bors@rust-lang.org> | 2017-11-27 17:13:20 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-11-27 17:13:20 +0000 |
| commit | 560a5da9f1cc7f67d2fc372925aef18c96c82629 (patch) | |
| tree | c70c06cc13258c729007fa48331c907443ca59ce /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 58e1234cddd996378cb9df6bed537b9c08a6df73 (diff) | |
| parent | d64a31882f6cdfcfbea82a257bb5cc64e6f7a7fc (diff) | |
| download | rust-560a5da9f1cc7f67d2fc372925aef18c96c82629.tar.gz rust-560a5da9f1cc7f67d2fc372925aef18c96c82629.zip | |
Auto merge of #46022 - matthewjasper:cannot-assign-twice-error, r=arielb1
Mir Borrowck: Parity with Ast for E0384 (Cannot assign twice to immutable) - Closes #45199 - Don't allow assigning to dropped immutable variables - Show the "first assignment" note on the first assignment that can actually come before the second assignment. - Make "first assignment" notes point to function parameters if needed. - Don't show a "first assignment" note if the first and second assignment have the same span (in a loop). This matches ast borrowck for now, but maybe this we should add "in previous loop iteration" as with some other borrowck errors. (Commit 2) - Use revisions to check mir borrowck for the existing tests for this error. (Commit 3) ~~Still working on a less ad-hoc way to get 'first assignment' notes to show on the correct assignment. Also need to check mutating function arguments.~~ Now using a new dataflow pass.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
