[doc] Be more clear on super() regarding multiple base classes methods (GH-21789) (GH-25706)

(cherry picked from commit 69a733bda3)

Co-authored-by: Andre Delfino <adelfino@gmail.com>

Co-authored-by: Andre Delfino <adelfino@gmail.com>
This commit is contained in:
Miss Islington (bot) 2021-04-28 18:13:12 -07:00 committed by GitHub
parent c4e503ed80
commit 8d47f92d46
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1631,7 +1631,7 @@ are always available. They are listed here in alphabetical order.
not found in statically compiled languages or languages that only support
single inheritance. This makes it possible to implement "diamond diagrams"
where multiple base classes implement the same method. Good design dictates
that this method have the same calling signature in every case (because the
that such implementations have the same calling signature in every case (because the
order of calls is determined at runtime, because that order adapts
to changes in the class hierarchy, and because that order can include
sibling classes that are unknown prior to runtime).