@propensive we have to play fast and loose with implicits. No guarantee of uniqueness, can always pass different one: http://blog.ezyang.com/2014/07/type-classes-confluence-coherence-global-uniqueness/ …
-
This Tweet is unavailable.
-
-
Replying to @puffnfresh
@puffnfresh "[...] can always pass different one" ... no, you can prevent that, that's the reason why its safer than Haskell.@propensive2 replies 0 retweets 0 likes -
Replying to @oxnrtr
@oxnrtr how do you prevent it? i.e., disallow https://gist.github.com/tpolecat/38e323101d050c91a88f … /@puffnfresh@propensive4 replies 0 retweets 0 likes -
Replying to @tpolecat
@tpolecat@puffnfresh@propensive Why would I want to prevent that? That's exactly the behavior I would implement, if it wouldn't exist.1 reply 0 retweets 0 likes -
Replying to @oxnrtr
@oxnrtr@tpolecat@puffnfresh@propensive Because you can achieve the same goal with less hack. It's a win that costs you nothing.1 reply 1 retweet 1 like -
Replying to @dibblego
@dibblego@oxnrtr@tpolecat@puffnfresh@propensive I am curious what you folks think of http://homepages.inf.ed.ac.uk/wadler/papers/implicits/implicits.pdf ….1 reply 1 retweet 0 likes -
Replying to @missingfaktor
@missingfaktor@oxnrtr@tpolecat@puffnfresh@propensive implicits are a known failed experiment, well before Scala. All part of the funny.1 reply 1 retweet 1 like -
Replying to @dibblego
@dibblego@oxnrtr@tpolecat@puffnfresh@propensive Any pointers on the literature that elaborates on their failed status?2 replies 0 retweets 0 likes
@missingfaktor @oxnrtr @tpolecat @puffnfresh @propensive You can also reason yourself to conclude, but seeing that often might be my bias.
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.