Hi. For H98, I prefer option (A). Option (B) gives an arbitrary dissimilarity with rangeSize and enumFromTo. They currently match the standard mathematical treatment of ranges such as i..j, which Chris Okasaki mentioned. I'm not saying that they're sacred, just that a shift to the style of option (B) is too far-reaching for H98. For any version of Haskell, I prefer that take n x and drop n x (when length x < n) should not immediately raise errors, in general. That would be too strict. It's arguable whether errors should be raised in the special case that x == []. How similar should drop 1 be to tail? Regards, Tom
- Re: drop & take [was: fixing typos in H... Matt Harden
- RE: drop & take [was: fixing typos in Haskel... Roberto E. Lublinerman
- Re: drop & take [was: fixing typos in Haskel... Marcin 'Qrczak' Kowalczyk
- Re: drop & take [was: fixing typos in H... Hamilton Richards
- Re: drop & take [was: fixing typos ... Ch. A. Herrmann
- Re: drop & take [was: fixing typos in Haskel... Marcin 'Qrczak' Kowalczyk
- RE: drop & take [was: fixing typos in Haskel... Brian Boutel
- Re: drop & take [was: fixing typos in H... Craig Dickson
- Re: drop & take [was: fixing typos ... Craig Dickson
- Re: drop & take [was: fixing typos ... Fergus Henderson
- RE: drop & take [was: fixing typos in Haskel... Tom Pledger
- RE: drop & take [was: fixing typos in Haskel... Brian Boutel
- Re: drop & take [was: fixing typos in H... Fergus Henderson
- Re: drop & take [was: fixing typos in Haskel... Marcin 'Qrczak' Kowalczyk
- Re: drop & take [was: fixing typos in Haskel... Marcin 'Qrczak' Kowalczyk
- Re: drop & take [was: fixing typos in Haskel... Marcin 'Qrczak' Kowalczyk
- Re: drop & take [was: fixing typos in H... Pablo E. Martinez Lopez
- Specialisation by constraint [was: drop &am... Tom Pledger
- RE: drop & take [was: fixing typos in H... Frank A. Christoph
- Re: drop & take [was: fixing typos in H... Jan Kort
- RE: drop & take [was: fixing typos in Haskel... Brian Boutel