On 4 June 2010 12:33, Ivan Lazar Miljenovic <span dir="ltr"><<a href="mailto:ivan.miljenovic@gmail.com">ivan.miljenovic@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Ozgur Akgun <<a href="mailto:ozgurakgun@gmail.com">ozgurakgun@gmail.com</a>> writes:<br>
[...]<br>
><br>
> What stops us from allowing alphanum characters appear in the Infix version<br>
> (after the colon)? Can't it be relaxed to only start woth a colon?<br>
<br>
</div>The definition. I believe this is probably to make parsing of<br>
"foo:<bar" (using your example below) unambiguous, the same as how<br>
symbolic operators can't contain alphanumeric characters, etc.<br>
<div class="im"><br></div></blockquote><div><br>I see.<br>Then people would need to put spaces between those things, right?<br>What a horrible consequence!<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
><br>
> So I want to be able to say something like:<br>
><br>
> data Expr = Expr :< Expr -- checks for LT betwen two Expr's<br>
> | Expr :<2 Expr -- a different implementation of the<br>
> same thing maybe<br>
> | Expr :<veryfast Expr -- and the veryfast implementation<br>
> of it<br>
<br>
</div>How does a data structure have a faster implementation? >_><br>
</blockquote><div><br><br>Well it might indicate to use a different function while evaluating the expression.<br>Still not a good example, I know.<br></div></div><br>Best,<br>Ozgur<br>