Re: References in XPath that can be representedbyastringandstill can be garbage collected

>> > rules for the order of evaluation of expressions - all expressions.
>>
>> Not all expressions.
>> The rules are the same as for expressions deriving their
>> values from node identity.
>
> I don't think so. For node identity, there is no issue with order of
> evaluation, the only constraint is some strictness about evaluating an
> expression the right number of times.

I think these are very close issues:

for
  $i in (1 to 10),
  $v in f:function-depending-on-node-id()
return
  ($i, $v)