diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2021-01-30 13:36:46 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-30 13:36:46 +0900 |
| commit | 7fa991fb8545d8b03f0ab953770cb4fa08921abc (patch) | |
| tree | 54c0955ab34bca2303c2807adf8738be0dfa1586 /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 91ea1cbc177e3ed460c5435092d1cc07e4423428 (diff) | |
| parent | 5e983d7b3f03e9243d905e0579f32be00170c9af (diff) | |
| download | rust-7fa991fb8545d8b03f0ab953770cb4fa08921abc.tar.gz rust-7fa991fb8545d8b03f0ab953770cb4fa08921abc.zip | |
Rollup merge of #81291 - sexxi-goose:fix-struct-update-functional-record-update-syntax-error, r=nikomatsakis
Support FRU pattern with `[feature(capture_disjoint_fields)]` In case of a functional record update syntax for creating a structure, `ExprUseVisitor` to only detect the precise use of some of the field in the `..x` part of the syntax. However, when we start building MIR, we 1. First, build the place for `x` 2. and then, add precise field projections so that only some parts of `x` end up getting read. When `capture_disjoint_fields` is enabled, and FRU is used within a closure `x` won't be completely captured, and therefore the first step will fail. This PR updates `mir_build` to create a place builder in the first step and then create place from the builder only after applying the field projection. Closes https://github.com/rust-lang/project-rfc-2229/issues/32 r? ``````@nikomatsakis``````
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions