diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-10-21 01:39:13 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-21 01:39:13 +0200 |
| commit | f8d1c3589e51061a3999e8de3bf59aeccfc06f5c (patch) | |
| tree | 21c587fabf04ab05cfb14d86fea744502ba11e79 /src/libstd/sys | |
| parent | 194d1935d393c635b620cf82bd299868e7bddce1 (diff) | |
| parent | f907fbe1a6676a26cfc893b78f0fffb4285f1e6c (diff) | |
| download | rust-f8d1c3589e51061a3999e8de3bf59aeccfc06f5c.tar.gz rust-f8d1c3589e51061a3999e8de3bf59aeccfc06f5c.zip | |
Rollup merge of #65592 - RalfJung:const-prop-comment, r=wesleywiser
clarify const_prop ICE protection comment This is based on discussion at https://github.com/rust-lang/rust/pull/64890/files#r334555787. That said, why are function arguments the only unsized locals that could remain uninitialized? Couldn't we also fail to initialize some local but still go on with const_prop, and then hit a line that takes a reference to that? Cc @wesleywiser @oli-obk ; I don't know enough about const-prop to understand why this can happen only for function arguments. ~~The PR includes https://github.com/rust-lang/rust/pull/64890; the only new commit is 05e4e6ba0d5.~~
Diffstat (limited to 'src/libstd/sys')
0 files changed, 0 insertions, 0 deletions