Revision as of 11:01, 11 October 2022 edit ButterCashier (talk \| contribs) Extended confirmed users, Rollbackers 33,551 edits Reverting edit(s) by 2409:4041:2E07:8DBA:0:0:649:611 (talk) to rev. 1115203130 by NineLord: non-constructive (RW 16.1) Tags: RW Undo ← Previous edit		Revision as of 07:05, 19 October 2022 edit undo WikiCleanerBot (talk \| contribs) Bots 1,007,735 edits m v2.05b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation) Tag: WPCleaner Next edit →
Line 234: Composition relation is more flexible as it may be changed on runtime, while sub-typing relations are static and need recompilation in many languages. Some languages, notably [[Go (programming language)\|Go]]<ref>{{cite web \|url=https://commandcenter.blogspot.com/2012/06/less-is-exponentially-more.html \|title=Less is exponentially more \|last1=Pike \|first1=Rob \|date=2012-06-25 \|accessdate=2016-10-01 }}</ref> and [[Rust (programming language)\|Rust]],<ref>{{Cite web \|title=Characteristics of Object-Oriented Languages - The Rust Programming Language \|url=https://doc.rust-lang.org/stable/book/ch17-01-what-is-oo.html#inheritance-as-a-type-system-and-as-code-sharing \|access-date=2022-10-10 \|website=doc.rust-lang.org}}</ref>, use type composition exclusively. ==Drawbacks==

Composition over inheritance: Difference between revisions