<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><blockquote type="cite" class="">On 27 Jul 2016, at 02:40 , James Noble <<a href="mailto:kjx@ecs.vuw.ac.nz" class="">kjx@ecs.vuw.ac.nz</a>> wrote:<br class=""><br class="">Here's a request: could people run this over their code:<br class=""><br class="">egrep "^(.*)method(.*))(.*)," `find . -name \*.grace` |grep -v \} | grep -vi test<br class=""></blockquote><div class=""><br class=""></div>What are you trying to accomplish with this?<div class=""><br class=""><blockquote type="cite" class="">(it won't find method decnls where the , is on a second line. but...)<br class=""><br class=""><blockquote type="cite" style="font-family: Times-Roman; font-size: 17px; font-style: normal; font-variant: 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;" class="">It is then still possible to state that the vararg formal will be bound to some unspecified object that supports iteration, but nothing else<br class=""></blockquote><br class="">which is how variadic parameters worked before, or originally.<br class=""></blockquote></div><div class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" style="font-family: Times-Roman; font-size: 17px; font-style: normal; font-variant: 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;" class="">(although personally I think it should just be a standard library list/array object...).<br class=""></blockquote></blockquote></div><div class=""><br class="">Actually, variadic parameters were bound to sequences, which <i class="">were</i> standard library objects. This caused horrible circular dependencies in the compiler, <br class="">since the code generator needed to know about a library that it might not have compiled yet …<br class=""> </div><div class="">Now that [ _ ] is no longer an operator, I don’t think that there is a big problem using them for both lineups and type parameters. But using ⟦ and ⟧ is so much more geeky! With luck, it will frighten non-geek people off of using type parameters at all, which is probably a good thing.</div><div class=""><br class=""></div><div class="">Our development version of the web IDE lets you type [[ (without a space) and translates it to ⟦. So I hope that the vinegar won’t be too strong. </div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Andrew</div><div class=""> </div><div class=""><br class=""></div></body></html>