<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The benefits of it far out weight the fears of having it.</span></div></blockquote></div>so what is the practical problem that's solved by final that convinced you?<div class=""><br class=""></div><div class="">I also would change the list of downsides and put "annoyance" on top — especially for those who don't care for theoretical improvement when they have to pay the price in form of more effort:</div><div class="">"If I don't want to subclass something, I just don't do it — why do I have to change the properties of the superclass?"</div><div class=""><br class=""></div><div class="">Also:</div><div class="">- structs are always final, inheritance is one of the major aspects of class. In many cases, the decision for class is made because of the ability to subclass.</div><div class="">- you can't subclass across module borders with the default visibility</div><div class="">In summary, final already is very common, and I don't see the need to push this further just because "inheritance" became old-fashioned lately.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Tino</div></body></html>