Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion src/libsyntax/parse/parser.rs
Original file line number Diff line number Diff line change
Expand Up @@ -3618,7 +3618,15 @@ impl<'a> Parser<'a> {
{
let (iattrs, body) = self.parse_inner_attrs_and_block()?;
attrs.extend(iattrs);
Ok(self.mk_expr(span_lo.to(body.span), ExprKind::TryBlock(body), attrs))
if self.eat_keyword(keywords::Catch) {

@Centril Centril Apr 10, 2019 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be preferable to ban any form of try { ... } $ident { .. } from a perspective of having maximum flexibility in the future.

@Kampfkarren Kampfkarren Apr 10, 2019 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should those all suggest match instead, or should that just be catch?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @estebank ^-- I would probably say yes, but that's more a diagnostics issue than future lang design flexibility.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking of the following case:

    let _ = try {
        true
    }
    let _ = ();

where the error is the lack of ;, which is why I'm a bit weary of suggesting the right syntax for every ident. The current output for this the following, which I feel doesn't hinder understanding more than complaining about an inexistent catch would:

error: expected one of `.`, `;`, `?`, or an operator, found `let`
 --> src/main.rs:7:5
  |
6 |     }
  |      - expected one of `.`, `;`, `?`, or an operator here
7 |     let _ = ();
  |     ^^^ unexpected token

let mut error = self.struct_span_err(self.prev_span,
"keyword `catch` cannot follow a `try` block");
error.help("try using `match` on the result of the `try` block instead");
Comment thread
estebank marked this conversation as resolved.
error.emit();
Err(error)
Comment thread
estebank marked this conversation as resolved.
} else {
Ok(self.mk_expr(span_lo.to(body.span), ExprKind::TryBlock(body), attrs))
}
}

// `match` token already eaten
Expand Down
10 changes: 10 additions & 0 deletions src/test/ui/try-block/try-block-catch.rs
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
// compile-flags: --edition 2018

#![feature(try_blocks)]

fn main() {
let res: Option<bool> = try {
true
} catch { };
//~^ ERROR keyword `catch` cannot follow a `try` block
}
10 changes: 10 additions & 0 deletions src/test/ui/try-block/try-block-catch.stderr
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
error: keyword `catch` cannot follow a `try` block
--> $DIR/try-block-catch.rs:8:7
|
LL | } catch { };
| ^^^^^
|
= help: try using `match` on the result of the `try` block instead

error: aborting due to previous error