mattrobenolt / mattrobenolt/alloconda
GC traverse/clear hooks for class payload references
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
Add GC traverse/clear hooks for alloconda class payloads holding py.Object references.
Motivation
- Payloads can store Python references (e.g. Writer.parent).
- Cycles can keep objects alive and skip
__del__cleanup.
Proposal
- Add opt-in GC traverse/clear hooks for alloconda classes.
- Provide helpers for payload types to declare py.Object fields to visit/clear.
- Ensure deinit still runs when GC collects.
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 inspecting the alloconda class payload implementation and the existing deinit paths, especially payloads that hold py.Object references such as Writer.parent. Determine how opt-in traverse and clear hooks can be declared for payload fields. Done means payload references are visited and cleared during GC, while deinit still runs for collected objects; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100