Paul Schoenfelder

> First, we need to define a trait for `ObjectStore`. This could look something like this: > > ```rust > pub trait ObjectStore { > /// Returns MAST forest corresponding...

@bobbinth FYI, we already support `exec.ROOT`, so that's good to go. We also already support adding compiled libraries to the `Assembler` to be linked against (I just wired up the...

This is actually one of the things I've fixed haha

I think having a dedicated node type for external references is likely to be more ergonomic (and efficient), but you've got the right idea in terms of how to handle...

> All makes sense. We will probably need to build a map Digest |-> NodeId during the compilation into MAST - but that can be discarded once the Program is...

@Overcastan I think you'll find it pretty easy to port this to #1277, if you look at how your implementation of `u32clz`, etc. was ported to the new structure, it's...

The 1.81 release looks like it will contain the stabilized `error_in_core` trait, and there is a draft PR in `thiserror` that implements the necessary changes there, but I'm not sure...

See [here](https://github.com/sagiegurari/cargo-make) for details on what you can do with `cargo make`. We use it in the compiler, so you can also reference our `Makefile.toml` and GitHub Actions jobs to...

> Yep - makes sense. One question: in some repos we already have Makefiles - would these be replaced with `cargo make`? That would be my recommendation, there's no need...

I think we should distinguish between `dyncall` and `dynexec` here. There are a lot of useful programs that will need `dynexec` in order to be compiled (essentially any language with...