mirror of
https://github.com/pybind/pybind11.git
synced 2024-11-14 09:34:46 +00:00
doc updates
This commit is contained in:
parent
09e22b4a17
commit
f53e300fbd
@ -526,14 +526,13 @@ The following example snippet shows a use case of the
|
|||||||
non-determinism and segmentation faults, hence it is worth spending the
|
non-determinism and segmentation faults, hence it is worth spending the
|
||||||
time to understand all the different options in the table above.
|
time to understand all the different options in the table above.
|
||||||
|
|
||||||
.. warning::
|
It is worth highlighting one common issue where a method (e.g. a getter)
|
||||||
|
returns a reference (or pointer) to the first attribute of a class. In this
|
||||||
pybind11 tries to eliminate duplicate addresses by returning the same reference object.
|
case, the class and attribute will be located at the same address in
|
||||||
If two addresses are the same, though they do not point to the same object semantically,
|
memory, which pybind11 will recongnize and return the parent instance
|
||||||
this may cause unexpected behaviour. An explicit policy should be used instead of
|
instead of creating a new Python object that represents the attribute.
|
||||||
relying on `automatic`.
|
Here, the :enum:`return_value_policy::reference_internal` policy should be
|
||||||
A common example is a reference to the first member of a class which has the same memory
|
used rather than relying on the automatic one.
|
||||||
location as its owning class.
|
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user