You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In eta.core.types, we have types like FileSequence that represent a sequence of files indexed by one numeric parameter, like /path/to/files/%05d.ext.
Currently, if one wants to declare that one is writing a sequence of, say, VideoLabels files, one must define a new concrete type VideoLabelsSequence to capture that.
It would be preferable to have a polymorphic type, say, Sequence, and the ability to write something like eta.core.types.Sequence<eta.core.types.VideoLabels>, which declares that you are expecting a sequence of VideoLabels files, without having to introduce a new concrete type in eta.core.types.
The text was updated successfully, but these errors were encountered:
In
eta.core.types
, we have types likeFileSequence
that represent a sequence of files indexed by one numeric parameter, like/path/to/files/%05d.ext
.Currently, if one wants to declare that one is writing a sequence of, say,
VideoLabels
files, one must define a new concrete typeVideoLabelsSequence
to capture that.It would be preferable to have a polymorphic type, say,
Sequence
, and the ability to write something likeeta.core.types.Sequence<eta.core.types.VideoLabels>
, which declares that you are expecting a sequence ofVideoLabels
files, without having to introduce a new concrete type ineta.core.types
.The text was updated successfully, but these errors were encountered: