@jonsterling @dibblego When I started Scala people said "use cake", it seemed to be the way. We quickly learned that it was actually painful
Just a reminder that #Scala cake pattern modules, are as a matter of fact, anti-modular.
#doublethink
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego@runarorama Famous ICFP Cake Party threw the cakes into Boston harbor:)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jonsterling Because gullible people include programmers and even programming language designers too.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jonsterling@dibblego See http://dl.acm.org/citation.cfm?id=1094815 … — even though the name "cake pattern" does not appear there. -
@jonsterling@dibblego (cake pattern = no explicit sharing constraints) ~ (inheritance = no explicit delegation). Tradeoffs are similar.
End of conversation
New conversation -
-
-
-
@dibblego Or is the modularity problem due to cake-specific things, such as objects-as-modules, first-class modules, or inheritance?
End of conversation
New conversation -
-
-
@jonsterling@dibblego Sharing constraints can be encoded: `val p: q.type /* add '= q' to satisfy it. */` -
@jonsterling@dibblego Just learned that (given enough dependent types) one can replace Haskell's t.c. coherence with sharing constraints. - Show replies
New conversation -
-
-
-
@Evanfchan I don't care about the answer to that question. It's a false dichotomy.
End of conversation
New conversation -
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.