[DRAFT] [API] Enrich supported dataclass values for pipeline templates
<tomclegg> tetron: is this an opportunity to "do whatever cwl does"?
<tetron> unfortunately I don't have a good answer, the current CWL spec is based on json schema, but the next draft is going to use arvo which has a different type system
<tetron> the minimum to do here is at least distinguish between floats and integers
<tetron> tomclegg: a quick glance at json schema suggests that it doesn't even go that far
<tetron> tomclegg: avro has int/long/float/double for 32/64 bit integers and floats respectively
<tetron> tomclegg: so, I would say use 64 bit types, but we can call them whatever
<tomclegg> yeah. the names 'long' and 'double' seem much less obvious/friendly than 'int' and 'float'. I think Go's approach is pretty good: if anyone actually wants to specify #bits, they might as well come right out and say int64, instead of "double what?"