Use frontend language when defaulting IR input path
When no --input is provided, the generate command builds the IR path using the target language (resolve_compile_output(..., &target_lang, ...)). If a user compiles from a different frontend language (e.g., gleam) and then generates to another target (e.g., scala), the IR is stored under out/<project>/compile/gleam, but generate will look under compile/scala and fail with “IR input path does not exist”. This breaks the default workflow whenever frontend and target differ; the default should be derived from the frontend language in config (or the compile output used by the last compile step), not the backend target.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #36 (comment)
When no
--inputis provided, the generate command builds the IR path using the target language (resolve_compile_output(..., &target_lang, ...)). If a user compiles from a different frontend language (e.g.,gleam) and then generates to another target (e.g.,scala), the IR is stored underout/<project>/compile/gleam, but generate will look undercompile/scalaand fail with “IR input path does not exist”. This breaks the default workflow whenever frontend and target differ; the default should be derived from the frontend language in config (or the compile output used by the last compile step), not the backend target.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #36 (comment)