Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:4
-
Epic Link:
-
Team:Data Release Production
Description
Currently pybind11 defaults to py::return_value_policy::copy or (py::return_value_policy::take_ownership) for (const) references (and pointers) respectively.
It would be better if it would require an explicit return_value_policy to be specified instead.
Investigate this further and potentially push changes upstream.
Attachments
Issue Links
- mentioned in
-
Page Loading...
Activity
That depends on how Jim Bosch feels about it. We can certainly complete the port without it, but it may help prevent issues later.
Pim Schellart [X] (Inactive)
added a comment - That depends on how Jim Bosch feels about it. We can certainly complete the port without it, but it may help prevent issues later. We can certainly complete the port without it
That sounds like the key information. I'll move it to DM-9155. 
3.5 years later, we haven't investigated, it hasn't caused any problems, and I don't think we have spare effort to push changes upstream. Won't Fix.
Is this essential to the immediate pybind porting work? If not, let's move it to the DM-9155 epic.