Provide a buffer initialization stage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes it helps if buffers can be initialized with certain values before a workflow begins running. A user can manually design the workflow in a way that ensures the buffers are initialized before any other node gets run, but this may take some careful thought on the user's part.
The initialization stage would be the complement of the cleanup stage. Where the cleanup stage runs after a workflow has finished running, the initialization stage would run before. Similar to cleanups, initializations are themselves workflows whose initial inputs are one or more buffers and whose final output is a trigger.
The only significant challenge is that in many cases initialization workflows will want to see the input value of the parent workflow. It is not clear how to generalize that visibility in a sound way. We will probably need to rely on InRef which was introduced in a more recent version of bevy.
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 reading the existing cleanup stage implementation and the referenced InRef change in Bevy. Determine how cleanup workflows receive buffers and triggers, then resolve how an initialization workflow should access the parent workflow's input. Done means the initialization lifecycle and input visibility are specified well enough to implement and test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100