Saxon

I think this was a consequence of the changes made in response to bug

https://saxonica.plan.io/issues/3287

We changed the way the constants were defined to try to eliminate the bottleneck identified by that user, and in the course of this we invoked a semi-automatic refactoring that removed the unused constants (unused within the product, that is).

The static initialisation of this class has caused problems in the past with deadlocks during class loading; it also often shows up on performance/memory profiles as a significant part of the initialization overhead. With the new mechanism of BuiltInAtomicType objects holding references to their corresponding SequenceTypes, I would really prefer to allocate all the SequenceType objects lazily on first reference.

I would suggest changing your extension functions so that instead of SequenceType.SINGLE_INT, they use BuiltInAtomicType.INT.one().

Sorry about the incompatibility. We have far too many interfaces like this that are "semi-public" - primarily intended for internal use but sufficiently useful to users that applications are likely to become dependent on them, and to break when we change them. Use s9api interfaces where you can, as we try very hard to keep these compatible.

Thank you for the explanation, it makes sense. Ok, will use BuiltInAtomicType methods instead.