> On Apr 27, 2017, at 3:35 AM, Slava Pestov via swift-dev
> wrote:
> Hi all,
>
> I’ve spent most of the last two days debugging various issues with property
> and subscript accesses on class-constrained existentials and I’ve just now
> realized the root cause is a much more fundamental issue.
And here’s a test case that crashes at runtime in Swift 3.1 and asserts on an
asserts-on build that does not involve protocol compositions, only protocol
refinement and a class constraint:
protocol P {
func bar()
}
// Comment out the 'class ,' to make the problem go away
protocol Q : class, P
Hi all,
I’ve spent most of the last two days debugging various issues with property and
subscript accesses on class-constrained existentials and I’ve just now realized
the root cause is a much more fundamental issue.
Consider the following code:
protocol P {
var x: Int { get set }
init()
