Add a reference to the name mangling description in the tutorial to the index. (GH-10138)

(cherry picked from commit c5eec4426d)

Co-authored-by: Andrés Delfino <adelfino@gmail.com>
This commit is contained in:
Miss Islington (bot) 2018-11-07 10:29:58 -08:00 committed by GitHub
parent 2911d4eb21
commit b949f74f4b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions

View File

@ -672,6 +672,9 @@ be treated as a non-public part of the API (whether it is a function, a method
or a data member). It should be considered an implementation detail and subject or a data member). It should be considered an implementation detail and subject
to change without notice. to change without notice.
.. index::
pair: name; mangling
Since there is a valid use-case for class-private members (namely to avoid name Since there is a valid use-case for class-private members (namely to avoid name
clashes of names with names defined by subclasses), there is limited support for clashes of names with names defined by subclasses), there is limited support for
such a mechanism, called :dfn:`name mangling`. Any identifier of the form such a mechanism, called :dfn:`name mangling`. Any identifier of the form