<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Wed, Dec 23, 2015, at 20:09, Andrey Tarantsov wrote:<br></div>
<blockquote type="cite"><blockquote><div>Isn't this proposal solving a problem that in practice doesn't exist or isn't common enough to be worth a language level fix?<br></div>
</blockquote><div> </div>
<div>Well I have a TextExpander macro that inserts "// override point" when I<br></div>
<div>type ;overp. Been marking all overridable methods this way for years. I<br></div>
<div>think it's an indication that the problem is worth solving.<br></div>
<div> </div>
<blockquote><div>I'm trying to find an example of a common problem - in any language - that would benefit by having final/sealed by default.<br></div>
</blockquote><div> </div>
<div>Understanding the code and reasoning about the class is easier when you<br></div>
<div>know the exact customization points.<br></div>
<div> </div>
<div>I do agree that this won't really prevent many actual bugs.<br></div>
<div> </div>
<div>A.<br></div>
<div> </div>
</blockquote><div>Those are good points and things I came to realize after I asked that. I don't have a Text Expander snippet but it is common in the code I work to have some kind of hack to inform what is intended to be overrided.<br></div>
<div> </div>
<div>Thanks for sharing, this is exactly the kind of answer (not because it is in favor of final) I was hoping to get when I asked.</div>
</body>
</html>