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 built the PyAnyMethods traits with the assumption that we might be able to use arbitrary_self_types as an off-ramp in the future. The traits seem to have been adopted well though it would be nice to remove them again for simplicity if possible.
The latest iteration of arbitrary_self_types is now feature complete on nightly and looks like there might be a stabilisation report soon: rust-lang/rust#44874 (comment)
Has anyone got some time / energy to experiment with this for our potential use in PyO3? As well as in PyAnyMethods, it might be useful in PyRef<MyClass> / Bound<MyClass> etc. for #[pymethods] receivers.
I would love to try, but I am experiencing a drought of time which is probably lasting until March 😢
We built the
PyAnyMethods
traits with the assumption that we might be able to usearbitrary_self_types
as an off-ramp in the future. The traits seem to have been adopted well though it would be nice to remove them again for simplicity if possible.The latest iteration of
arbitrary_self_types
is now feature complete on nightly and looks like there might be a stabilisation report soon: rust-lang/rust#44874 (comment)Has anyone got some time / energy to experiment with this for our potential use in PyO3? As well as in
PyAnyMethods
, it might be useful inPyRef<MyClass>
/Bound<MyClass>
etc. for#[pymethods]
receivers.I would love to try, but I am experiencing a drought of time which is probably lasting until March 😢
cc @adetaylor
The text was updated successfully, but these errors were encountered: