David Hewitt
David Hewitt
Thank you for making progress on this one. There's a measurable perf boost in the ordering operator benchmarks and I guess similarly this is a win for most `#[pymethods]`, so...
> The second option sounds very interesting. Switching the lifetime and introducing it via `PyClassGuard` could make an easier migration than breaking `PyRef`/`PyRefMut`. This makes me wonder if something like...
As for this here, it seems then that the migration path we quite like here is to add new `PyClassGuard` types. We can probably introduce those already and implement `FromPyObjectBound`...
> ... but maybe if we accept two traits, the second trait becomes `FromPyObjectAttached`? That is at least a new angle for us to experiment with! `FromPyObjectBound` which we already...
Shall we close this in favour of #5233 ?
One alternative possibility here is that we change the `pyclass` internals so that instead of only being able to store `T` they can also store a range of different containers...
To follow up here - I was thinking that to allow `Arc` conversions we might want to pair it with a `#[pyclass(storage)]` option which is able to store arcs in...
`#[pyclass(storage)]` being my not fully fleshed out idea from https://github.com/PyO3/pyo3/pull/5233#issuecomment-3089194417
Closing as duplicate of #5137
I believe #84 has solved this same problem, will close here. Thanks again.