News for hackers. Stuff that matters.
Re:Pitfalls in Haskell by Morgawr on Monday August 22, 2016 @11:27AM (#12336980)
This assumes that you have an isA and an isB function. This forces me to write such a function which I might not have and in case of very very very large data types (like ~20-30, if not more, constructors) it becomes unwieldy and very messy.
Re:Pitfalls in Haskell by dllthomas on Monday August 22, 2016 @11:37AM (#12337068)
It's probably less work than duplicating the cases, and ideally you can give a more meaningful name to the whole "isA or isB" construct - especially when you have a lot of constructors!