diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2022-04-26 13:22:30 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-26 13:22:30 +0200 |
| commit | f908391136c9797235ad6de11be46114b654ca61 (patch) | |
| tree | ea79973fddcecb09a0d0da50ca79ff9d23591f3e /src/librustdoc/html/static/js/source-script.js | |
| parent | a818173e6339a394bcac8236a66cee49a876bb4b (diff) | |
| parent | 941e19468ab6239a220ec3214c584e281636a26d (diff) | |
| download | rust-f908391136c9797235ad6de11be46114b654ca61.tar.gz rust-f908391136c9797235ad6de11be46114b654ca61.zip | |
Rollup merge of #96400 - JakobDegen:shallow-init-docs, r=Dylan-DPC
Correct documentation for `Rvalue::ShallowInitBox` As a part of the big MIR docs PR, I had added a comment indicating that `Rvalue::ShallowInitBox` is disallowed after drop elaboration, but this is not true (no idea why I thought it was). Codegen has support for it, and trying to enforce this rule in the validator causes compiling core to ICE on the very first `box` statement. That being said, this `Rvalue` probably *should* be banned after drop elaboration - it doesn't seem like it's still useful for much. However, I do not have time right now to actually go investigate how difficult a change that is to make, so in the meantime fixing the docs to reflect the current situation seems like the right step. r? rust-lang/mir-opt
Diffstat (limited to 'src/librustdoc/html/static/js/source-script.js')
0 files changed, 0 insertions, 0 deletions