diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-02-22 14:58:02 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-22 14:58:02 +0100 |
| commit | bcb7dce75c7b566f091b9f2d5486d7aa162337de (patch) | |
| tree | 9abc00f9070e678a6023e26310e3e3c41a5d210c /src/rustllvm/RustWrapper.cpp | |
| parent | 42b9a046d46ef00ecd3a13135f3cd5d7044218b6 (diff) | |
| parent | 9312ca10b6cd672c4fa1da4b4a3cc232f7d7dde6 (diff) | |
| download | rust-bcb7dce75c7b566f091b9f2d5486d7aa162337de.tar.gz rust-bcb7dce75c7b566f091b9f2d5486d7aa162337de.zip | |
Rollup merge of #58555 - scottmcm:try-2015, r=Centril
Add a note about 2018e if someone uses `try {` in 2015e
Inspired by https://github.com/rust-lang/rust/issues/58491, where a `try_blocks` example was accidentally run in 2015, which of course produces a bunch of errors.
What's the philosophy about gating for this? The keyword is stably a keyword in 2018, so I haven't gated it for now but am not mentioning what the keyword _does_. Let me know if I should do differently.
Resolves #53672
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions