Might it pay to think about a common interface (à la GHC.Prim) that all compiler back-ends should implement (instead of having a bunch of pragmas for each of them) and that would help us get consistent semantics for our programs? I'm still not sure what to do about the strict vs. non-strict issues, but this might help us go in the right direction.<div>
<br><br><div class="gmail_quote">On Mon, Dec 5, 2011 at 2:22 PM, Alan Jeffrey <span dir="ltr"><<a href="mailto:ajeffrey@bell-labs.com">ajeffrey@bell-labs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 12/05/2011 01:19 PM, Nils Anders Danielsson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2011-12-05 19:02, Nils Anders Danielsson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Note that with this approach the type-checker is free to reduce seqs,<br>
because the reduction removes the thunk.<br>
</blockquote>
<br>
This argument seems to be incorrect. Besides, does anyone use seq in a<br>
strict language?<br>
</blockquote>
<br></div>
I think the idea is to allow interoperability between strict and lazy implementations of Agda. In a strict implementation, seq would be a no-op.<span class="HOEnZb"><font color="#888888"><br>
<br>
A.</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
Agda mailing list<br>
<a href="mailto:Agda@lists.chalmers.se" target="_blank">Agda@lists.chalmers.se</a><br>
<a href="https://lists.chalmers.se/mailman/listinfo/agda" target="_blank">https://lists.chalmers.se/<u></u>mailman/listinfo/agda</a><br>
</div></div></blockquote></div><br></div>