Open Michael-F-Bryan opened 3 years ago
Each step in a Rune needs to explicitly mention the type of its outputs.
pipeline: content_image: capability: IMAGE outputs: - type: u8 dimensions: [1, 384, 384, 3]
However, using a dict with type and dimensions keys can get a bit verbose (even when you write the list as [1, 384, 384, 3] instead of the normal bullet-point notation).
type
dimensions
[1, 384, 384, 3]
As an alternative, it'd be nice to use a shorthand.
pipeline: content_image: capability: IMAGE outputs: - u8[1, 384, 384, 3]
This could be implemented in a backwards compatible way by switching the Type struct to an untagged enum (in serde parlance).
Type
serde
CC: @f0rodo
I think we also need a types field
types
types: $image_raw_type: u8[255, 3] ... outputs: $image_raw_type
Something like that
Each step in a Rune needs to explicitly mention the type of its outputs.
However, using a dict with
type
anddimensions
keys can get a bit verbose (even when you write the list as[1, 384, 384, 3]
instead of the normal bullet-point notation).As an alternative, it'd be nice to use a shorthand.
This could be implemented in a backwards compatible way by switching the
Type
struct to an untagged enum (inserde
parlance).CC: @f0rodo