<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 Aug 29, 2018, at 3:47 AM, Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; 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; text-decoration: none; float: none; display: inline !important;" class="">So the extra polymorphism in the function space would be invisible.</span></div></blockquote></div><br class=""><div class="">Not quite. It would be visible to anyone who cares about the type of (->), which would now be more elaborate. This includes people using type-level type application (<a href="https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0015-type-level-type-applications.rst" class="">https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0015-type-level-type-applications.rst</a>), whose implementation is under way by a student of mine, and anyone looking at the TypeRep of (->). I'm not overly concerned by these bumps, but I don't want to overclaim that everyone who doesn't use -XLinearTypes will be utterly unaffected.</div><div class=""><br class=""></div><div class="">Richard</div></body></html>