Project

Profile

Help

Bug #5067

open

Stability of collection ordering

Added by Michael Kay over 2 years ago. Updated 4 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
External resources
Sprint/Milestone:
-
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.

Actions #1

Updated by Michael Kay over 2 years ago

  • Description updated (diff)
Actions #3

Updated by Michael Kay 4 months ago

  • Category set to External resources

Please register to edit this issue

Also available in: Atom PDF