Implementation inheritance and default parameters scatter application logic throughout a code base and make local reasoning impossible. They do save you effort now, but you will pay for it later—with interest.
-
-
Replying to @jdegoes
Quite he opposite: lack of implementation inheritance means multiple randomly mutated copies of the same code will be scattered all around the code base, making maintenance impossible. To reason about inheritance, search for the set of applicable methods in the code browser.
1 reply 0 retweets 1 like -
I disagree, you can obtain DRY without implementation inheritance.
1 reply 0 retweets 1 like
Replying to @FilippoDeLuca @jdegoes
The kind of DRY you can achieve with inheritance can't be expressed without reimplementing inheritance. That said, I'm usually more interested in inheriting the laws, and having refinement proofs for the implementations.
2:56 PM - 5 Feb 2019
0 replies
0 retweets
2 likes
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.
Read my blog!