3 ms·
I see your point about being explicit. I think ideally the specification would be precise enough for the user to conclude: "If this is a specification conformin
by zelphirkalt 6y ago
I see your point about being explicit. I think ideally the specification would be precise enough for the user to conclude: "If this is a specification conforming Scheme implementation, then this must be a tail call." I was under the impression, that this is the case with the Scheme specification, but I might be wrong, as I am not very knowledgeable in terms of the specification. If it is not so specific about what exactly becomes a tail call, then I would say, that it would be great to have an explicit way to tell the interpreter or compiler, that you want something to definitely be a tail call.
- kazinator 6y ago... and if you have that declaration mechanism, then it can easily work for any call in any position whatsoever!!! So that further separates the concept "tail call" from "call in tail position". Any position can be the tail position if we just wave he right magic wand at it, so the concept becomes meaningless. All we are left with is the style of call: returning versus goto-like.