Of course, in this particular case, worrying about the overhead of manipulating an Integer when you are in the process of jumping through the hoops to put your thread to <b>sleep</b> is somewhat silly. ;)<div><br></div><div>
In general though, using Ints by default is a reasonable performance compromise.</div><div><br></div><div>-Edward<br><br><div class="gmail_quote">On Wed, Mar 30, 2011 at 2:59 PM, Daniel Fischer <span dir="ltr">&lt;<a href="mailto:daniel.is.fischer@googlemail.com">daniel.is.fischer@googlemail.com</a>&gt;</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 Wednesday 30 March 2011 20:47:37, Wolfgang Jeltsch wrote:<br>
&gt; Can’t Integer be implemented in a more efficient way that it’s done<br>
&gt; currently?<br>
<br>
</div>Theoretically, sure. Practically, everything above a minor speedup would be<br>
very hard, I think.<br>
And, as Johan mentioned, Integers can&#39;t be unpacked, I don&#39;t see how that<br>
could be achieved, so for IntMap and the like, performance would be<br>
drastically worse even if Integer manipulation itself got significantly<br>
faster.<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</div></div></blockquote></div><br></div>