You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add a table to the documentation that explains with trait and method to use to convert one wrapper type to another. This is complementary to #374.
For example you use ToPyObject::to_object to convert &PySomeNativeType to PyObject and there's AsPyRef to convert PyObject and Py<T> to PyRef<T>s.
The text was updated successfully, but these errors were encountered:
You beat me to it, I was going to suggest the same thing.
I was thinking there should be an N x N grid, possibly with color-coded backgrounds to indicate things like "zero cost conversion" and whether the transformation is safe.
We should add a table to the documentation that explains with trait and method to use to convert one wrapper type to another. This is complementary to #374.
For example you use
ToPyObject::to_object
to convert&PySomeNativeType
toPyObject
and there'sAsPyRef
to convertPyObject
andPy<T>
toPyRef<T>
s.The text was updated successfully, but these errors were encountered: