diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-09-05 03:59:47 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-09-05 03:59:47 +0200 |
| commit | c195145f565159c84e61b2f2c6f4ef2bebd5b66f (patch) | |
| tree | da1869c326cb19d956e93b0121beab5674a338bb /src/libsyntax | |
| parent | 24f0778341691661121d093d4767a937fdb8ebed (diff) | |
| parent | b03d3dc478ba13f405cf9a877a4894de096a1cc1 (diff) | |
| download | rust-c195145f565159c84e61b2f2c6f4ef2bebd5b66f.tar.gz rust-c195145f565159c84e61b2f2c6f4ef2bebd5b66f.zip | |
Rollup merge of #64123 - danielhenrymantilla:add_comment_about_uninit_integers, r=Centril
Added warning around code with reference to uninit bytes Officially, uninitialized integers, and therefore, Rust references to them are _invalid_ (note that this may evolve into official defined behavior (_c.f._, https://github.com/rust-lang/unsafe-code-guidelines/issues/71)). However, `::std` uses references to uninitialized integers when working with the `Read::initializer` feature (#42788), since it relies on this unstably having defined behavior with the current implementation of the compiler (IIUC). Hence the comment to disincentivize people from using this pattern outside the standard library.
Diffstat (limited to 'src/libsyntax')
0 files changed, 0 insertions, 0 deletions