enum_pipline
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!
println!("init"), Operations::Run(delta) => println!("do work") } } } fn do_work() { let my_op_pipeline = vec![ Operations::Init, Operations::Allocate(1.0, 1.0), Operations::Init, Operations::Run(1.0), ] .into_pipeline(); my_op_pipeline.execute(); // prints: // init // allocate something // init // do work } ">
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 do_work() { let my_op_pipeline = vec![ Operations::Init, Operations::Allocate(1.0, 1.0), Operations::Init, Operations::Run(1.0), ] .into_pipeline(); 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.
TODO
- finish the proc-macro stuff
- document the proc-macro
- add example directory
License
MIT
10.9k Jan 6, 2023
12 Jun 7, 2023
2.9k Dec 28, 2022
12.1k Jan 2, 2023
7.8k Jan 8, 2023
2.9k Jan 7, 2023
30 Dec 10, 2022
5k Jan 4, 2023
172 Dec 23, 2022
14 Oct 31, 2022
5 Aug 31, 2023
5 Sep 6, 2023
184 Dec 22, 2022
5k Jan 9, 2023
21 Nov 28, 2022
266 Jan 2, 2023
939 Jan 5, 2023
30.7k Jan 7, 2023
40 Dec 20, 2022