Explore ability to use with DataFlow

I'm just thinking about different use cases. I think over time we will also need to create blocks for DataFlow - https://learn.microsoft.com/en-us/dotnet/standard/parallel-programming/dataflow-task-parallel-library or at least just keep this in mind use case

Anti — 01/21/2024 5:49 PM
About TPL. Last time i heard about it it was something like 2010... Didn't know that it is still in use. Should be quite easy to wrap our chain links into ActionBlocks
Also i'm thinking of some sort of separate repository for prompts. Every model is requiring a little bit different prompts. So having a repository with premade templates and tags seems to be a good idea.

HavenDV — 01/21/2024 6:31 PM
We use TPL every day. This is an async/await Task and the generated compiler code hidden behind it
But DataFlow is the official library for more complex connections based on this
Anti — 01/21/2024 6:33 PM
thought TPL = DataFlow. I was using it 10 years ago, so don't remember terms. As i rememebr, it's bunch of blocks with LinkTo methods
HavenDV — 01/21/2024 6:34 PM
Yes, and communications between blocks can occur in parallel without the user having to explicitly manage this. We just have to keep it in mind so we don't reinvent it.

The issue names no files, tests, or entry points. Start by reviewing the linked Dataflow documentation and the project's existing chain-link abstractions. A concrete integration scope and acceptance criteria are not defined, so there is no verifiable “done” state yet.