Open Radar

 
Summary:
When using "catch as NSError" in a regular function then the catch clause is considered exhaustive.
When using "catch as NSError" in a closure then the closure is inferred as "throws" because the catch is NOT considered exhaustive.

This results in the following compilation error when calling or passing the closure: "call can throw, but it is not marked with 'try' and the error is not handled"

Steps to Reproduce:
1. Copy attached example code into a Playground
2. You'll get the error "call can throw, but it is not marked with 'try' and the error is not handled"

Expected Results:
"catch as NSError" should be considered exhaustive and the closure not be marked as "throws".

Actual Results:
The closure is erroneously inferred as "throws"


Attached file:

import Foundation

func funcWhichThrows() throws {}

func testWithClosure() {
	{ () -> Void in
		do {
			try funcWhichThrows()
		}
		catch _ as NSError {
			// catch all as NSError
		}
	}()
}

func testWithoutClosure() {
	do {
		try funcWhichThrows()
	}
	catch _ as NSError {
		// catch all as NSError
	}
}