[bitc-dev] Retrospective: The Issues with Type Classes
Jonathan S. Shapiro
shap at eros-os.org
Sun Apr 15 17:00:54 PDT 2012
On Sun, Apr 15, 2012 at 4:36 PM, Sandro Magi <naasking at higherlogics.com>wrote:
> A JIT would solve all of Jonathan's problems, except keeping the TCB
> small and auditable. At the moment, the situation is very much: small
> TCB, inlining, separate compilation, pick any two.
Yes, though JIT has a huge systemic cost when it is applied to *all* of the
programs in a system.
I have no objection to using JIT techniques. In fact, I think that doing so
is a *very *good idea. What I want to avoid is designing a language whose *
only* sensible compilation method relies on JIT. Maintaining the ability to
do separate compilation is a necessity, in my view.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bitc-dev