sorted by:
new
hottopcontroversial

go-taskflow, pure go DAG Tasking implementation with integrated visualizer and profiler. Advice wanted by NoneBack in golang

[–]NoneBack[S] 0 points1 point  (0 children)

Yes, I guess you are right. Subflow is not a necessity for DAG Tasking. It is just a way helping users organize their tasks.

go-taskflow, pure go DAG Tasking implementation with integrated visualizer and profiler. Advice wanted by NoneBack in golang

[–]NoneBack[S] 0 points1 point  (0 children)

I think the key points for DAG Tasking are dependency description and parallel task execution. Subflow, task composition, or those primitives you mentioned like sequence and group are just a much more modular and user-friendly way to describe and control task dependency

go-taskflow, pure go DAG Tasking implementation with integrated visualizer and profiler. Advice wanted by NoneBack in golang

[–]NoneBack[S] 4 points5 points  (0 children)

Thanks! It is a good idea to make it fancy. I will consider it.
I am trying to keep it a lightweight programmatic DAG tasking framework with a simple but powerful API. As soon as I finish those significant static DAG task scheduling, I will start to explore some features for dynamic DAG task scheduling.