Re: PROPOSAL: Some more 'Applicative' combinators
The more general question, which stems from a certain degree of ignorance on my part, is what uses folks have found for Alternative at all outside of parsing. --S On Jan 8, 2008, at 4:43 AM, apfelmus wrote:
Iavor Diatchki wrote:
Bryan O'Sullivan wrote:
Why not make the task specificity clearer, with a separate Control.Applicative.Parsing module?
+1
Now _this_ would definitely suggest that they are only good for parsing which would be misleading.
Would it? I mean, I currently don't know a second use case for them. Preferably, the names like skipMany , endBy , sepBy etc. should still make sense in the new context.
Regards, apfelmus
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
Sterling Clover wrote:
The more general question, which stems from a certain degree of ignorance on my part, is what uses folks have found for Alternative at all outside of parsing.
Alternative is the generalization of MonadPlus, so empty and <|> are useful for lists and Maybe at least. But I'm not sure whether many :: Alternative f => f a -> f [a] and friends have any uses outside of parsing. Regards, apfelmus
participants (2)
-
apfelmus -
Sterling Clover