mattrobenolt / mattrobenolt/alloconda
Refcount ergonomics for py.Object copies
Open
Nobody has claimed this yet.
core
fastproto
- Dominant language
- Zig
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Improve refcount ergonomics for py.Object copies.
Motivation
- Manual incref when copying py.Object is easy to miss.
- This is a footgun when storing payload state.
Proposal
- Provide explicit helpers (e.g. Object.clone/Object.retain) to clarify ownership.
- Consider wrapper types that make ownership intent obvious at call sites.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the py.Object copy and ownership behavior described in the issue, then identify the relevant Zig and Python-extension entry points. Compare the proposed clone/retain helpers and wrapper types, and define the ownership semantics and call-site expectations before implementation; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100