Reece H. Dunn

That just means that in order to traverse an IEnumerator, you need to write: ```csharp IEnumerator enumerator = createGenerator(); while (enumerator.MoveNext()) { T current = enumerator.Current; // ... } ```...

I think it would be useful to try and write different generator functions that cover the different expected uses/patterns so we can work out what properties and associated semantics are...

@michaelhkay Yes. The record interface defined here is an iterator. What we (Dimitre and I) are proposing is in effect lazy or dynamic sequences where the (possibly infinite) values are...

I think it would make sense to keep this issue about the record-based interface. The discussion on coroutines, yield, etc. should be a separate issue. With my `fn:sequence` proposal, you...

Note that the spec changes to separate the element and type namespaces has been reverted following comittee review of the behaviour. That would need reinstating or revising to make work...

I would be happy with `for entry ...` for maps, so ForExpr/FLWORExpr would support: 1. `for ...` for sequences (existing); 2. `for member ...` for arrays (new in the draft...

The terms `key` and `value` are widely used in computer science literature in reference to maps and other similar constructs (such as key-value data stores). Those names are also used...

Note that the `for {$x, $y} ...` syntax is similar to the map part of the decomposition syntax I proposed in https://github.com/expath/xpath-ng/pull/8.

The XPath 4.0 discussion is in issue #37 for the `for {$x, $y} ...` map syntax. I propose keeping this about the `for key $k value $v in ...` and...

Yes, that's what I had in mind with the CSV example. It should also apply to arrays and maps -- if there is one value left, assign that value to...