Open Radar

 
Summary:
When a function with a protocol as a generic constraint is sent a mismatched parameter, Xcode project simply segment faults or in playground,  crashes the LLDB RPC server; note that the function must also access the protocol's associated type.

Steps to Reproduce:
1. Create a generic function that uses a protocol with associated types as its generic constraint.
2. In order to also access the protocol's associatedtype, create a simple escaping completion handler that does so.
The function signature should look something like this

func load<R: Resource>(resource: R, completion: @escaping (R.Content?) -> ()) 

3. Call the function with a mismatched parameter. 
load(resource: 1) { res in
}

Expected Results:
I expected the Swift compiler to saying something in the lines of "Cannot convert type value 'Int' to expected argument type 'Resource'

Observed Results:
The Xcode project simply spits out a segmentation fault exit 11. In playground, Xcode simply says an internal error has occurred and that the LLDB  RPC server has crashed.

Version:
Xcode 8.3.3 (8E3004b)
macOS Sierra Version 10.12.5