Bruno Kolenbrander

Thanks for the suggestion! One thing that is tricky is deciding what this function should look like. Should it accept just a single integer type, or should it accept multiple...

> @mejrs if this is not being worked on happy to take it on? Please do!

One way to fix it would be to get `auto_traits` and `negative_impls` working on stable and make our own auto trait, but that seems far off. Something we could do...

I'm thinking I'd like to use the `nightly` feature for this. Would it be OK to gut out specialization?

One thing I'm semi worried about is an interaction like this: **pyo3's lib.rs** ```rust #![feature(auto_traits, negative_impls)] pub unsafe auto trait Foo{} impl !Foo for Python src\main.rs:6:61 | 6 | let...

> But the error could be better, so let's keep this open for an improvement. This should be fairy straightforward, right? Just emit a custom error if the receiver is...

Yeah I personally use that to avoid copying in my `__iter__` implementations. ```rust #[pyclass(name = "Index")] pub struct PyCacheIndex { inner: Option, } #[pymethods] impl PyCacheIndex { fn __iter__(&mut self,...

> I think the right solution is for PyO3 to automatically define `__match_args__` I feel that this asserts that if you create two instances of a class using the same...

Can you expand on your use case for this? I wonder what the right api for this will be, because I really don't want to have functions with that many...

Thanks, this is excellent feedback :) It is mentioned in the [api documentation](https://docs.rs/pyo3/0.15.1/pyo3/struct.Python.html#obtaining-a-python-token). but not really anywhere in the guide. This is something I initially found annoying as well, I...