[bitc-dev] Retrospective: The Issues with Type Classes
bklooste at gmail.com
Sun Apr 15 21:35:07 PDT 2012
> This is not true. It is true that you cannot inline across the dynamic
> library boundary without a JIT system, but that was never my concern. My
> concern was the inability to inline **ground operations** such as integer
An important distinction .
But these form a handful of common instructions surely you could
handle this with some nasty hack eg a mini Jit when you load the app
that parses it and replaces calls to xyz . Or even better in the
compiler if you see A+B and both types are bit arrays output abc in a
preoptomization step (just like intrinsics) - an inelegant hack yes
but small and would cover most cases very quickly and probably better
than the common solution of languages creating special value / basic
types ( which is a bigger but effective hack) .
Isnt not inlining dlls a bigger issue ? eg a dll can have Math. Min
and other common constructs .
More information about the bitc-dev