Chris Okasaki wrote: > For the people that share this sentiment, can you please > explain why ints that are too big should not similarly > give an error? I can see both being ok, or both being > errors. I just don't see why one should be ok and the > other an error. IMHO, both should be errors. If we really need, we can provide takeSloppy, takeBackwards, etc, but the default should be a tight as possible to catch errors. I still believe that take and drop should satisfy the compositional laws on legal arguments. Regards, Tommy
- RE: drop & take [was: fixing typos in Haskell-... BYRNE, Peter
- RE: drop & take [was: fixing typos in Has... S. Alexander Jacobson
- Re: drop & take [was: fixing typos in... Dr. Mark E. Hall
- RE: drop & take [was: fixing typos in Has... Simon Peyton-Jones
- Re: drop & take [was: fixing typos in... Ola Fosheim Grøstad
- Re: drop & take [was: fixing typo... Pablo E. Martinez Lopez
- Re: drop & take [was: fixing ... Ola Fosheim Grøstad
- Re: drop & take [was: fixing typos in Has... Chris Okasaki
- Re: drop & take [was: fixing typos in... Tommy Thorn
- Re: drop & take [was: fixing typos in... Philip Wadler
- Re: drop & take [was: fixing typo... Joe Fasel
- Re: drop & take [was: fixing typo... Chris Okasaki
- Re: drop & take [was: fixing ... Philip Wadler
- Re: drop & take [was: fixing ... Joe Fasel
- Re: drop & take [was: fixing ... Fergus Henderson
- Re: drop & take [was: fixing typos in... D. Tweed
- Re: drop & take [was: fixing typo... D. Tweed
- Re: drop & take [was: fixing typos in... Matt Harden
- RE: drop & take [was: fixing typos in Has... Roberto E. Lublinerman