This issue has #286 (I/O support) as a prerequisite. Although Hydra is primarily intended as a library, once the build system has been promoted (#416), it will have a major CLI component as well. The task at hand is to plan and organize this CLI, and to consider other capabilities apart from build tasks (like translating Hydra JSON into various targets). This CLI would have subcommands like:
hydra transform [source-lang] [target-lang] [source-loc] [target-loc]hydra validate [lang] [loc]hydra infer [source-loc] [target-loc]hydra benchmark [test-suite] [source-loc]hydra compute [lang] [source-loc] [target-loc]hydra list modules [packages]- etc.
Whether the hydra command is confined to a single host at a time, or calls across hosts, is TBD.
This issue has #286 (I/O support) as a prerequisite. Although Hydra is primarily intended as a library, once the build system has been promoted (#416), it will have a major CLI component as well. The task at hand is to plan and organize this CLI, and to consider other capabilities apart from build tasks (like translating Hydra JSON into various targets). This CLI would have subcommands like:
hydra transform [source-lang] [target-lang] [source-loc] [target-loc]hydra validate [lang] [loc]hydra infer [source-loc] [target-loc]hydra benchmark [test-suite] [source-loc]hydra compute [lang] [source-loc] [target-loc]hydra list modules [packages]Whether the
hydracommand is confined to a single host at a time, or calls across hosts, is TBD.