I just noticed that because of BitC's implicit tuplization, the keyword "tuple" actually doesn't need to be a keyword at all for purposes of expressions: (define tuple (lamda x x)) causes (tuple a) to do the right thing. The only reason that we need TUPLE to be a keyword is because it also has a role in types and pattern matching. Amusing. shap