diff options
| author | bors <bors@rust-lang.org> | 2022-05-01 13:10:21 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-05-01 13:10:21 +0000 |
| commit | 508e0584e384556b7e66f57b62e4feeba864b6da (patch) | |
| tree | 1d17b65bf57ed67312cb5232af75b6d21e72dc65 /compiler/rustc_codegen_llvm/src/common.rs | |
| parent | 637b3f68079fc81db9bfd2c0f8f306c892680d25 (diff) | |
| parent | b317ec1697fa3d8d095ea99b7180ae6eab9f77af (diff) | |
| download | rust-508e0584e384556b7e66f57b62e4feeba864b6da.tar.gz rust-508e0584e384556b7e66f57b62e4feeba864b6da.zip | |
Auto merge of #96376 - scottmcm:do-yeet, r=oli-obk
Add `do yeet` expressions to allow experimentation in nightly Two main goals for this: - Ensure that trait restructuring in https://github.com/rust-lang/rust/issues/84277#issuecomment-1066120333 doesn't accidentally close us off from the possibility of doing this in future, as sketched in https://rust-lang.github.io/rfcs/3058-try-trait-v2.html#possibilities-for-yeet - Experiment with the *existence* of syntax for this, to be able to weight the syntax-vs-library tradeoffs better than we can right now. Notably the syntax (with `do`) and name in this PR are not intended as candidates for stabilization, but they make a good v0 PR for adding this with minimal impact to compiler maintenance or priming one possible name choice over another. r? `@oli-obk` The lang `second` for doing this: https://github.com/rust-lang/lang-team/issues/160#issuecomment-1107896716 Tracking issues - Lang, https://github.com/rust-lang/rust/issues/96373 - Libs-api, https://github.com/rust-lang/rust/issues/96374
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/common.rs')
0 files changed, 0 insertions, 0 deletions