On LangChain there is the kwargs where it's passed from front to back, with the nature of Python's dynamic typing this kwargs can be reused by many layers from agent, to chain until model.
However, to have an idiomatic Go developer experience, that model is not ideal. If we talk about the perfect way, it should use a functional option pattern.
Need more research on how this model will looks like.
On LangChain there is the kwargs where it's passed from front to back, with the nature of Python's dynamic typing this kwargs can be reused by many layers from agent, to chain until model.
However, to have an idiomatic Go developer experience, that model is not ideal. If we talk about the perfect way, it should use a functional option pattern.
Need more research on how this model will looks like.