feat(query): implement scalar functions and XML Schema casts (#563) - #585
Merged
remiceres merged 1 commit intoSep 10, 2026
Merged
Conversation
|
Test Results 427 files 427 suites 25s ⏱️ Results for commit 4dd4a38. |
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements #563 in the native
core.next.querypipeline: SPARQL scalar built-ins, XML Schema constructors and SPARQL expression type-error handling.Validation
./gradlew test: 2,934 tests, zero failures/errors/skips.functions: 75/75 pass. Cast evaluation: 5 pass + 1 indeterminate; all seven cast syntax tests also pass.The 239 remaining SPARQL failures are pre-existing cases outside this issue. The additional indeterminate case is not claimed as passing: upstream
cast-decimal.srxrewrites four directly projected source literals. The companion harness PR continues executing it, recognizes only that exact discrepancy and preserves the original JUnit failure. No official fixture is changed and no core behavior is tailored to its erroneous expected source terms.Integration order
Merge this PR into feature/corese-next first, then merge corese-stack/corese-w3c#27. The harness uses the existing native parser only to identify computed numeric projections; numeric value comparison remains independent of Corese's numeric implementation. Its scoped comparison is justified by the upstream discussion, without relaxing directly projected RDF-term identity.