copper-project/copper-rs

feature: User friendly way to notify a lifecycle violation in the runtime

Open

#1,091 opened on May 10, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (97 forks)auto 404
enhancementerror_handlinggood first issuehelp wanted

Repository metrics

Stars
 (1,428 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem statement

Today we have several levels of APIs for the runtime that allows a full control from the user of the framework over the lifecycle of it.

The issue is that the user can put the stack in a bad state without noticing: for example calling start_all_tasks twice or mixing it with application.run

Proposed solution

Add a small enum based state machine to track the validity of those lifecycle changes and emit an error accordingly.

Alternatives considered (optional)

Make that debug only but this should be so small it might not worth it

Impact / scope (optional)

  • Affected crates, platforms, or features:

Additional context (optional)

Contributor guide

Research direction
Implement a small enum based state machine to track the runtime lifecycle state (e.g., Idle, Running, Stopped). Add checks in lifecycle methods (start all tasks, application.run, etc.) to emit errors or panics for invalid transitions. Use the type system to enforce valid transitions at compile time where possible.
Tech stack
rust
Domain
backendoperating systemsembedded iot
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70