Asymmetric Visiblity and Final properties #3828
Conversation
What is the issue here? |
PhD issue. The |
I suppose for the moment just leave it an open a PhD issue, as it should track nesting (because I imagine this being an issue outside of |
|
I addressed everything above aside from the sentence-per-line bits. That sounds like it's not a formal convention yet, and it's non-trivial to do, so I'd rather hold off until/unless there's some policy decision on it to follow. Anything else to address before we merge this? |
Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de>
|
(Rebased to try and fix the build.) |
Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de>
| </itemizedlist> | ||
| <para> | ||
| When a class extends another, the child class may redefine | ||
| any property that is not <literal>final</literal>. When doing so, |
There was a problem hiding this comment.
Maybe there should be a link to final keyword here.
Feels like we should add more keywords entities to doc-base/entities/global.ent
First stab at documenting asymmetric visibility and final properties. (Technically final properties came in with hooks, but that's a much bigger task and it does impact aviz, so I included it here.)