@MosRobinson @puffnfresh @djspiewak No, it's just a well-accepted inductive argument. Bad ideas never believed good are not worth a paper.
-
-
-
-
Replying to @dibblego
@dibblego@puffnfresh@djspiewak given there are papers saying "local instances are useful, let's do them", a rebuttal would be valuable1 reply 0 retweets 0 likes -
Replying to @MosRobinson
@MosRobinson@puffnfresh@djspiewak I know of no such thing, except for some Scala nonsense not worth considering. Which do you mean?3 replies 0 retweets 0 likes -
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
@MosRobinson @puffnfresh @djspiewak Or I could provide an instance of:
class HasTheNewType t where
theNewType :: Iso' t TheNewType
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.