On Thu, Dec 15, 2011 at 02:23, Gregory Crosswhite <[email protected]>wrote:
> On Dec 15, 2011, at 3:36 PM, Antoine Latter wrote:
>
> Even
> the operators at hand ('many' and 'some') are partial in parsing, but
> I'm not prepared to throw them out.
>
>
> Okay, I must confess that this straw man has been causing my patience to
> get a little thing. *Nobody* here is saying that many and some should be
> thrown out, since there are clearly many contexts where they are very
> useful. The *most* that has been suggested is that they should be moved
> into a subclass in order to make it explicit when they are sensible, and
> that is *hardly* banning them.
>
This.
I was always under the impression that the Haskell Way was to capture
constraints in the type system instead of letting them be runtime failures;
here we have some combinators that appear to require an additional
constraint, and active opposition to describing that constraint in the
type!
--
brandon s allbery [email protected]
wandering unix systems administrator (available) (412) 475-9364 vm/sms
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe
