diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-08-09 01:38:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-08-09 01:38:36 +0200 |
| commit | 87fb0ad4850ad710bb53440a12186006b498e785 (patch) | |
| tree | 0235c6e12166debd6990519714e3c3291041570c /src/libsyntax/parse/parser/module.rs | |
| parent | c9dd9309f2bc3a6885ab599ea2c771c85fc9346b (diff) | |
| parent | 48fbf4891a138edbaf2142ff9121c298c2750164 (diff) | |
| download | rust-87fb0ad4850ad710bb53440a12186006b498e785.tar.gz rust-87fb0ad4850ad710bb53440a12186006b498e785.zip | |
Rollup merge of #63387 - Centril:async-block-control-flow-tests, r=cramertj
Test interaction between `async { ... }` and `?`, `return`, and `break`
Per the second checkbox in https://github.com/rust-lang/rust/issues/62121#issuecomment-506884048, test that `async { .. }` blocks:
1. do not allow `break` expressions.
2. get targeted by `return` and not the parent function.
3. get targeted by `?` and not the parent function.
Works towards resolving blockers in #63209.
r? @cramertj
Diffstat (limited to 'src/libsyntax/parse/parser/module.rs')
0 files changed, 0 insertions, 0 deletions