4 ms·
For example I'd be happy if I could generate structs dynamically, based on string input. This would mean that we could automatically create true struct-based c
by samuell 11y ago
For example I'd be happy if I could generate structs dynamically, based on string input.
This would mean that we could automatically create true struct-based components with channel fields from the shell like syntax used in the examples in the README (like "echo > {o:foo}" to write to an out-port named "foo"), so that connecting an out-port to an in-port would go like:
Process2.InFoo = Process1.OutFoo
This is not possible with Go's reflection though, so right now, based on these shell like patterns, we can only populate maps (InPorts and OutPorts) of the process, such that the above code example becomes:
Process2.InPorts["foo"] = Process1.OutPorts["foo"]
- sbinet 11y agogenerating structs at runtime might land for go-1.7: https://go-review.googlesource.com/#/c/9251/4 https://go-review.googlesource.com/#/c/9251/4
- samuell 11y agoThat would be awesome.
- erikpukinskis 11y ago> For example I'd be happy if I could generate structs dynamically, based on string input. I don't understand why you'd want to do that. That sounds like an architecture you are excited about, not a problem you are trying to solve. Can you give me some context?
- samuell 11y agoThe reason is a practical one: Struct fields will show up in auto-completion. This is in our experience surprisingly important when doing iterative workflow development, to lower the amount of silly typo errors, which can waste a lot of cluster compute hours etc.