lambdaclass / lambdaclass/spawned
Add link and monitor operations for actors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 59
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Erlang-style process relationships, adapted to Spawned's type system (no Pids — uses ActorRef<A> and Recipient<M>).
Linking (bidirectional):
- When a linked actor stops, the other is notified (and stopped, unless trapping exits)
start_linked()— start an actor linked to the caller
Monitoring (one-way):
- Observer receives a notification when the monitored actor stops
monitor()→MonitorRefdemonitor(monitor_ref)
Exit trapping:
trap_exit()— convert linked exit signals into messages instead of stopping
Design notes:
- No
Pidtype — link/monitor targets are identified viaActorReforRecipient - Exit notifications delivered as messages to the actor's handler (exact message type TBD during implementation)
- Foundation for supervision (#133, #134)
Part of Phase 3 (Supervision Trees) — see docs/ROADMAP.md.
Contributor guide
No contributing guide indexed for this repository
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 with docs/ROADMAP.md and inspect the existing ActorRef and Recipient APIs mentioned in the issue. Clarify the exit-notification message type and the link, monitor, and trapping semantics before implementation. Done means the requested operations work consistently and provide the foundation described for supervision trees.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100