<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 Jan 22, 2023, at 1:12 AM, David Feuer <<a href="mailto:david.feuer@gmail.com" class="">david.feuer@gmail.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="">That's what ML calls the "value restriction", right?</span></div></blockquote></div><br class=""><div class="">No, ML's value restriction is unrelated to this conversation. ML's value restriction says that all polymorphic variables (top-level or otherwise) must syntactically be values -- not, say, function calls. The "value-ness" check might end up similar, but the motivations are distinct.</div><div class=""><br class=""></div><div class="">Richard</div></body></html>