Jason,<br><br>I am trying to use haskell in the analysis of bio data. One of the main reasons I wanted to use haskell is because lazy I/O allows you to see a large bio-sequence as if it was a string in memory. <br>In order to achieve the same result in an imperative language I would have to write lots of error-prone iterators. I saw lazy I/O as a very strong point in favor of Haskell.<br>
<br>Besides the space leaks that can occur and that are a bit difficult to find for a newbie like me, are there any other reasons to avoid Lazy I/O?<br><br>Arnoldo.<br><br><div class="gmail_quote">On Sat, Mar 13, 2010 at 6:46 PM, Jason Dagit <span dir="ltr">&lt;<a href="mailto:dagit@codersbase.com">dagit@codersbase.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div class="im">On Thu, Mar 11, 2010 at 3:44 PM, Arnoldo Muller <span dir="ltr">&lt;<a href="mailto:arnoldomuller@gmail.com" target="_blank">arnoldomuller@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Daniel,<br><br>Thank you so much for helping me out with this issue!<br><br>Thanks to all the other answers from haskel-cafe members too! <br><br>As a newbie, I am not able to understand why zip and map would make a problem...<br>


<br>Is there any link I could read that could help me to understand why in this case<br>zip and map created a leak? What are some function compositions that should be <br>avoided when doing lazy I/O?<br></blockquote><div>

<br></div></div><div>Actually, it&#39;s lazy I/O itself that should be avoided.</div><div><br></div><font color="#888888"><div>Jason</div></font></div>
</blockquote></div><br>