handle changed signature of FunctionDefinition
make sort optimization robust to more complex expressions
handle new saxon expression for xxx[n]
use saxon 9.5 (depends on local lib for now)
saxon 9,5 optimizes not(path) -> empty(path) ?
saxon fixed my TODO! optimizing not() into empty()
did saxon change its int->integer type promotion?
nice - Saxon fixed some error repetition
Saxon XdmValue changed a bit, adapting to Sequence.toString()
use saxon 9.5.1-2
use saxon 9.5.1-2
merged trunk back to saxon 9.5 branch and fixed compilation problems; some tests still fail
empty type now reported as ErrorType?
wording of error message changed
test invalidated by benign change in Saxon compiler behavior
fix compilation, warnings to work w/saxon 9.5
saxon 9.5 added a new opto here
replaced lux:field-values() w/lux:key()
fixed tests after Saxon query rewriting changed for this case
fixing up query test after Saxon changed a path from child to parent, which we no longer optimize