O language designers, don't make use of "private"/"protected" items a hard error. Make it a warning, at worst, or preferably just make "private" a kind of documentation of intent: http://funcall.blogspot.com/2019/12/i-think-you-left-something-out.html …
-
-
But if private is just a lint, or is overridable in any way, then you open a huge can of worms whereby even *private* modifications to A can break derived classes without warning. Never mess with name resolution!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.