<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 1, 2017, at 3:34 AM, Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com" class="">simonpj@microsoft.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><b style="font-family: 'Times New Roman', serif; font-size: 16px; font-style: normal; font-variant-caps: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Calibri, sans-serif;" class=""> </span></b><span style="font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Calibri, sans-serif;" class="">Who is acting there. Just Ben? Or are there bits Richard needs to help with?</span></div></blockquote></div><br class=""><div class="">Ben has done the real heavy lifting, with me opining on this bit or that. From what Ben says, it's very close.</div><div class=""><br class=""></div><div class="">There is a small bit of new work to be done to prefer Type over Constraint when solving for Typeable (my step 2), but that can't be hard.</div><div class=""><br class=""></div><div class="">If I'm released (for now) from #11715, what's the next priority for me?</div><div class=""><br class=""></div><div class="">Richard</div></body></html>