Align socket receive and control argument binding - #9668

Summary

• Share recv_into/recvfrom_into keyword binding through the VM's existing ArgSpec helper, preserving buffer export and numeric conversion order.
• Return immediately from zero-length recv and recv_into, including on closed sockets, as CPython does.
• Bind sendto and setsockopt arguments before conversion, retain original arguments through I/O, and acquire sendto's buffer export before converting flags without holding its data lock across callbacks.

Only production Rust files change. Existing special no-keyword and sendto overload diagnostics remain.

Evidence and validation

Checked CPython 3.15 source (Modules/socketmodule.c: sock_recv_guts, sock_recv_into, sock_recvfrom_into, sock_sendto, and sock_setsockopt). Bounded CPython 3.15.0 probes using only an owned socketpair confirmed:

• Both into-methods accept buffer, nbytes, and flags keywords.
• Buffer rejection precedes numeric callbacks; valid numeric callbacks precede duplicate/unknown keyword errors.
• Numeric callbacks can mutate exported buffer contents.
• Zero-byte recv and recv_into return immediately, including after closing the socket.
• sendto rejects an invalid buffer before invoking a flags callback.
• Invalid setsockopt arity does not invoke numeric callbacks.

rustfmt and git diff --check passed. Exact-head cached patches for #9638, #9640, and #9642 each apply cleanly over this change.

Passed on Linux against main 0b081b0283987c7b2d79327dd481f403d515580b:

• cargo check -p rustpython-vm -p rustpython-host_env -p rustpython-stdlib --features rustpython-stdlib/threading --locked --offline -j1
• cargo clippy -p rustpython-vm -p rustpython-host_env -p rustpython-stdlib --features rustpython-stdlib/threading --locked --offline -j1 -- -D warnings

RustPython runtime tests, the full Rust suites, Python suites, and other-platform testing were not run. CPython probes establish reference behavior, not execution of the patched RustPython interpreter.

Known limits

The receive methods already had a text-signature mismatch with CPython's keyword support. Their representation now becomes generic (*args, **kwargs); this patch does not repair introspection metadata. Writable-buffer error wording remains that of the shared buffer helper rather than claiming exact CPython wording.

The zero-byte results above were observed on Linux. On non-poll platforms CPython checks high-descriptor selectability before returning zero, so these observations do not establish blanket cross-platform equivalence.

Independent source review passed with no blocker.

Integration note

#9651 changes ArgSpec::parse_with from Fn to FnMut. This change exposes that existing helper and deliberately does not duplicate #9651's callback change. There is one adjacent-line textual conflict: preserve pub fn parse_with from this change and mut check: impl FnMut from #9651. The receive parser remains compatible with either callback signature.

AI assistance

The source investigation, patch, reference probes, and this draft were prepared with OpenAI Codex assistance under the maintainer's direction. Human review is requested before merge.

Summary by CodeRabbit

• Bug Fixes
  • Socket receive operations now return immediately with an empty result when given a zero-length buffer.
  • Receive operations validate requested byte counts, including negative and oversized values, with appropriate errors.
  • Socket send methods now enforce their supported argument counts and reject keyword arguments where unsupported.