Generalize `Routing.Match` combinators

Question

Closed this issue 7 years ago · 6 comments

I don't think any of these need to be monomorphic and can instead be defined in terms of MatchClass.

Answer 1 · 2018-03-22T13:39:50.000Z

eitherMatch would have to be added to the class I think, or the constraint on the class would have to be strengthened.

Alternative proposal too: we get rid of the class and only have the monomorphic versions 🙂

Answer 2 · 2018-03-26T16:25:42.000Z

How is eitherMatch different than either (const (fail ...)) pure? I agree that the class is unnecessary.

Answer 3 · 2018-03-26T16:27:40.000Z

Same with optionalMatch. How is it different than map Just a <|> pure Nothing?

Answer 4 · 2018-03-26T16:29:51.000Z

optionalMatch is fine, I'm not sure I understand how either fail pure works though? You need to bind, hence my comment about the constraint.

Answer 5 · 2018-03-26T16:32:42.000Z

Oh I see, yes you are right. We should just remove the class. I don't see what we gain from using it.

Answer 6 · 2018-05-14T16:57:14.000Z

Resolved in the 0.12 branch