<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 6, 2022, at 8:00 AM, Chris Dornan <<a href="mailto:chris@chrisdornan.com" class="">chris@chrisdornan.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Richard are you satisfied that my example program is invalid under PolyKinds?</span></div></blockquote></div><br class=""><div class="">Yes. But I think as we've started to piece together, the real problem in this example is a missing superclass constraint on Typeable, not a fundamental shortcoming of PolyKinds. (I do acknowledge that extra polymorphism can introduce trouble, but given the fact that PolyKinds introduces parametric polymorphism -- unlike the ad hoc polymorphism of OverloadedStrings -- I think these cases should be rare.)</div><div class=""><br class=""></div><div class="">It would be interesting to see whether fixing Typeable in this way fixes other problems Chris has run into.</div><div class=""><br class=""></div><div class="">Richard</div></body></html>