While it is unfortunate that I seem to get deeper and deeper into that topic... - it should be noted that data size matters most (pervasive use expected) - the design is leaning towards multiple functional closures - both together suggest to use a classical virtual interface, without much ado - yet parameters must be copyable values, to allow for evaluation graphs and snapshots - so this turns out as yet another use case for ''polymorphic values'' - furthermore, fluid usage requires flexible conversions between result values - given the situation with numeric value types and strings, this implies ''to build a visitor'' 🠲 ''putting that work aside for the moment, since I need to focus on my IO_URING research (for FrOSCon 26)'' |
||
|---|---|---|
| .. | ||
| parameter-domain-test.cpp | ||
| parameter-test.cpp | ||