This is a tracking issue for the work remaining to complete the support for __dunder__ (aka "protocol") methods in #[pymethods].
As per the proposal in #1864, the current intention is to have a working but experimental implementation of this in 0.15. If any feedback from this implementation is ok, I'd suggest to deprecate #[pyproto] in 0.16 or 0.17. If we're happy with the whole implementation earlier / later we can always adjust these aims.
The items outstanding after #1864
This is a tracking issue for the work remaining to complete the support for
__dunder__(aka "protocol") methods in#[pymethods].As per the proposal in #1864, the current intention is to have a working but experimental implementation of this in 0.15. If any feedback from this implementation is ok, I'd suggest to deprecate
#[pyproto]in 0.16 or 0.17. If we're happy with the whole implementation earlier / later we can always adjust these aims.The items outstanding after #1864
__dunder__at the Python level, so we'll need to design one__sequence_getitem__methods etc to be explicit. See also Allow taking slices when implementing PySequenceProtocol __getitem__ #1855multiple-pymethodsfeature__delete____anext____aiter____index____int____float____invert__(maybe) better argument extraction errors (if there's an error, the generated code won't say which argument failed, athough that's probably obvious as most these methods take at most one argument).__call____new__/__init__?