Hi Srayan, On Fri, Oct 24, 2025 at 7:07 PM Srayan Jana <[email protected]> wrote: > > So the idea would be > Currently, the process is > Guile -> Hoot -> WASM > But, once Hoot becomes part of Guile itself, you could possibly do > Guile -> Hoot -> LLVM or Guile -> Hoot -> C or Guile -> Hoot -> Cranelift or > whatever. > So Hoot could become a way to convert Guile bytecode to different possible > backends > Does that sound about right?
Kinda sorta. What I'm trying to say is that I think the earliest phase of Hoot's compilation pipeline, the creation and lowering of a "library group", could be extracted and used for whole-program compilation to other targets. Hoot takes the input program, gathers up all the required libraries into a library group, and then transforms the whole thing into a big letrec in Tree-IL form. https://codeberg.org/spritely/hoot/src/branch/main/module/hoot/library-group.scm#L939 - Dave
