Remove usage of `cfg` message from `Field` component
Opened this issue · 1 comments
emil14 commented
It's possible to have normal inport like path
that takes list<string>
What if user pass incorrect path? Should Field
have err
outport? No, it should panic. User should not use field in the first place. We need to add it to its description.
Problems
Runtime overhead
This is simplicity vs performance kind of tradeoff
- We need to allocate a message container which is a little bit bigger than native go slice
- We need to use network transmission machinery to make it work