Provides a way to use enums to describe and execute ordered data pipelines. 🦀🐾
I needed a succinct way to describe 2d pixel map operations for a game I'm working on. I wanted callers to be able to easily determine all possible operations (hence enum), with per-operation data (hence variants), and their operation-specific logic (proc-macro coming soon). This is what I came up with!
```rs use enum_pipeline::{ Execute, IntoPipelineVec };
enum Operations { Allocate(f32, f32), Init, Run(f32) }
impl Execute for Operations { fn execute(self) { match self { Operations::Allocate(x, y) => println!("allocate something"), Operations::Init => println!("init"), Operations::Run(delta) => println!("do work") } } }
fn dowork() { let myoppipeline = vec![ Operations::Init, Operations::Allocate(1.0, 1.0), Operations::Init, Operations::Run(1.0), ] .intopipeline();
my_op_pipeline.execute();
// prints:
// init
// allocate something
// init
// do work
} ```
There are variants for pipelines with global data as well (passed as an argument to execute), and I'm working on a proc-macro that can generate the boilerplate match logic, shelling out to different user provided functions for each operation.
MIT