Sean T Allen

It should be possible to know that we have a "lambda type thing" at the point of the error and change the message to "couldn't find 'string' in 'lambda f'"...

Two of our runner tests currently fail verification. We'll need to fix those (and other errors that might be hidden by those failures) before this is merged.

@jemc added.

This shouldnt be merged until we fix all the associated issues that cause CI to fail.

I would love to be able to have recursive types. There's a really old issue opened by me for it. That said as @jasoncarr0 said, we should fix the "BOOM!"...

This is definitely coming from an `else` that has a "jump away" like `error` or `return`

@jemc I'm not at all good with the compiler. Do you have any insights on fixing the current assertion failure?

@jemc ping.

@jemc says he remembers (he thinks) that in subtype.c there's logic to handle two types that have the same constraints, they might not be super or subtype without knowing more....

@sgebbie this seems like a reasonable addition that doesn't need to go through the RFC process (@ponylang/committer's can you weigh in)? I would also be open to an RFC detailing...