On Thu, Mar 22, 2012 at 12:53 AM, Iain Sandoe
> conceptually, the issue is that there are multiple sets of built-ins
> (potentially, one set for each runtime, and the sets are of different
> sizes). Thus, it's not just a case of turning these into regular built-ins,
> without some mechanism to cater for overloading or presence/absence of
> particular ones.
I don't understand this. We're committed to one runtime per
compilation, right? If so, then we should create only one of the sets
at any time.