Re: Issue: TAIL-RECURSION-OPTIMIZATION (Version 1)

[masinter.pa@Xerox.COM]

The X3J13 body seems willing (eager) to give implementors the leeway to make
small concessions in semantics in the name of performance. 

This seems like a relatively small concession given the negative association
with the assembly-language hacker's anathema of "self-modifying code".

I think it is marginally OK to leave the issue name alone.... 

Isn't this strongly related to FUNCTION-COERCE-TIME? I'm in favor of lazy
function coerce time for FUNCALL and agressive function coerce time for
car-of-form calling. That is, implementations should assume early binding when
it appears as the car of form, and late binding when it appears 'FOO.  If you
really want late binding, you can say (FUNCALL 'FOO x y), right?

I don't know if it makes sense to link the issues, but the two together make
more sense than either one alone.