balacij

I don't think the build times haven't been very problematic recently, cache hits are frequent. The main issue with our Actions seems to be GitHub network errors (lol). Should we...

Unrelated to the discussion above: I don't think we're going to get around everything that needs to be ultimately be done, but we might be able to make things faster...

We should remember @smiths' [comment](https://github.com/JacquesCarette/Drasil/issues/3483#issuecomment-1591995934) too. The TeX builds only need to run when the `stable/**.tex` files are changed.

Was this just outdated? Do we need to keep the old branch?

What do you mean by 'fully automated' @cd155? Your work for the IVPs seems to make it quite smooth. There might be alternative ways, but I think that we wouldn't...

I like the idea @smiths brought up about InstanceModels needing to be concrete enough such that we can generate code. If we try to think of 'concrete enough' using words...

Hmm, ok, I think that makes sense. To be clear, does this mean that 'concrete' and 'abstract' are terms that are attached only with respect to a particular target language...

Related to #3307: We have a few [code-related](https://github.com/JacquesCarette/Drasil/tree/master/code/drasil-lang/lib/Language/Drasil/CodeExpr) [chunks](https://github.com/JacquesCarette/Drasil/blob/master/code/drasil-lang/lib/Language/Drasil/Chunk/CodeVar.hs) in `drasil-lang` that I [started moving](https://github.com/JacquesCarette/Drasil/commit/05a9e473642136ad25843c5f44bf29f916cb30ee) to `drasil-code`, where I think they should belong. However, I'm blocked by a circular dependency...

I think the `drasil-code` style is also more in-tune with the semantics paper/"describe syntax with a semantic domain in mind" style. Seeing this idea through, an alternative view of `drasil-printers`...

If we consider chunks to be theory presentations (theories definitions in CAS 760 or the unified theories we've been discussing recently), then I think almost any theory would be able...