@MosRobinson @puffnfresh @djspiewak I know of no such thing, except for some Scala nonsense not worth considering. Which do you mean?
-
-
Replying to @dibblego
@dibblego@puffnfresh@djspiewak the relation to orphaned instances is interesting. I use orphan instances for QuickCheck.Arbitrary or ppr4 replies 0 retweets 0 likes -
Replying to @MosRobinson
@MosRobinson@puffnfresh@djspiewak Honestly, I'd rather have the discussion about how to turn that into practice. First, dismiss bad ideas.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@djspiewak need orphan type classes for that, otherwise forced to put instances with data declarations1 reply 0 retweets 0 likes -
Replying to @MosRobinson
@MosRobinson@puffnfresh@djspiewak Use newtype instead.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@djspiewak but that changes the interface of my module, doesn't it?7 replies 0 retweets 0 likes -
Replying to @MosRobinson
@MosRobinson@puffnfresh@djspiewak I'm genuinely disinclined to debunk every ridiculous idea on the internet and I'm sympathetic, not sorry2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@djspiewak I'm still not convinced that orphan instances are wrong1 reply 0 retweets 0 likes -
Replying to @MosRobinson
@MosRobinson@puffnfresh@djspiewak Do you accept there is a non-zero penalty?1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@djspiewak I accept that there is the possibility of writing multiple instances. is that what you mean?2 replies 0 retweets 0 likes
@MosRobinson @puffnfresh @djspiewak The non-zero penalty is way more than that, but that's all I need to debunk it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.