Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sequence types need to be polymorphic #365

Open
brimoor opened this issue Dec 18, 2019 · 0 comments
Open

Sequence types need to be polymorphic #365

brimoor opened this issue Dec 18, 2019 · 0 comments
Labels
enhancement Code enhancement

Comments

@brimoor
Copy link
Contributor

brimoor commented Dec 18, 2019

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.

@brimoor brimoor added the enhancement Code enhancement label Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Code enhancement
Projects
None yet
Development

No branches or pull requests

1 participant