[ska]

I can't make sense of what you are trying to say. In c++ you typically have no access whatsoever to the compiler at runtime. Through dynamic linking and some hacking about you can do this but it is all very non-standard.

In lisps you very typically have complete access to the compiler, though this is not universal. Resource limits on a running process are a separable issue.

[hellofunk]

We are talking about the resources of the machine and which of those resources are available during compile time compared to those which are available at runtime.

[ska]

Yes, but you start off with an incorrect premise, and it's hard to understand what point you are trying to make.

In a very typical lisp system, for example, exactly the same resources would be available at runtime as your original compile (in fact, the boundary between these two is pretty fuzzy and often might be the same process anyway)

Likewise, C++ typically doesn't have any runtime access to compilers at all, so what resources are available to them or not is a bit moot.

If the point is that you might deploy on a different machine or configuration, well - that's true, but I can't see the relevance.

You might be pointing out some oddities of Clojure, I suppose, but that's not a great model for "typical lisp".

[hellofunk]

Indeed my experience is mostly with Clojure, which I mentioned because my parent commenter referred to ClojureScript. Glad to know a "normal" lisp handles this differently.