New automatic return value policy for cat() and make_tuple(), fixed an ambiguity issue

This commit is contained in:
Wenzel Jakob
2016-04-14 14:26:13 +02:00
parent 2e03a5857c
commit 8bd31c71e4
3 changed files with 16 additions and 5 deletions

View File

@@ -418,6 +418,9 @@ functions. The default policy is :enum:`return_value_policy::automatic`.
| :enum:`return_value_policy::automatic` | Automatic: copy objects returned as values and take ownership of |
| | objects returned as pointers |
+--------------------------------------------------+---------------------------------------------------------------------------+
| :enum:`return_value_policy::automatic_reference` | Automatic variant 2 : copy objects returned as values and reference |
| | objects returned as pointers |
+--------------------------------------------------+---------------------------------------------------------------------------+
| :enum:`return_value_policy::copy` | Create a new copy of the returned object, which will be owned by Python |
+--------------------------------------------------+---------------------------------------------------------------------------+
| :enum:`return_value_policy::take_ownership` | Reference the existing object and take ownership. Python will call |