<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br>On 20 Mar 2014, at 18:23 , James Noble <<a href="mailto:kjx@ecs.vuw.ac.nz">kjx@ecs.vuw.ac.nz</a>> wrote:<br><br><blockquote type="cite"><blockquote type="cite" style="font-family: Times-Roman; font-size: 17px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;">That said, I LIKE using type to mean set of methods and with their types. I believe that it's what type OUGHT to mean, in an OO language. But the "type theorists" don't agree ...<br></blockquote><br>and that's what it means in Grace, and will continue to mean in Grace. <br></blockquote><br><div><br></div><div>Good. Hence my proposal that we write</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><b>const</b> Boolean = <b>type</b> {&& (SelfType) -> SelfType, || (SelfType) -> SelfType, ... }</div><div><br></div><div><b>const</b> is like <b>def</b>, but you can't override it in sub-objects, and the value must be knowable at compile time.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Andrew</div><div><br></div></body></html>