<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 Mar 26, 2018, at 5:54 PM, Roman Leshchinskiy <<a href="mailto:rleshchinskiy@gmail.com" class="">rleshchinskiy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""> C <inputs> \ <outputs></span></div></blockquote></div><br class=""><div class="">I had been trying to figure out how to get \ involved, and this is the way. Thanks! It does require that all inputs come before all outputs, which might not be true for constructors:</div><div class=""><br class=""></div><div class="">data T a where</div><div class=""> MkT :: forall b a. b -> T a</div><div class=""><br class=""></div><div class="">Here, `b` is an output while `a` would be an input. And in many cases constructors designed with visible type application in mind will want to put existentials ("outputs") before universals ("inputs"). If we ever did the C <inputs> \ <outputs> in the future, I suppose we could just say that such constructors will have their type variables reordered, perhaps issuing a warning if someone writes a mis-ordered constructor.</div><div class=""><br class=""></div><div class="">In any case, I'm glad that this discussion has changed your mind about accepting this proposal.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Richard</div></body></html>