Actions
Bug #5067
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Stability of collection ordering
Start date:
2021-08-23
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
The spec says that by default collections are stable, so processing the same collection twice should give the same result.
It also says that a collection is a sequence (not a set).
This is difficult to reconcile with Saxon's use of multi-threading to process the items in a collection, which makes the order of processing unpredictable. Perhaps we should be doing multi-threading within the same constraints as xsl:for-each
with a threads
attribute, where the results are delivered in the original order.
Problem arose from consideration of test case cbcl-collection-002
where in Saxon-CS we are delivering the (integer) contents of the collection in an arbitrary order.
Please register to edit this issue
Actions