Skip to content

Conversation

@Ostrzyciel
Copy link
Member

Issue #253

I also did a small refactor to implement this without too many hacks.

This adds some if/elses in the writer handler, but these should be extremely easy to optimize away by the JIT or the CPU branch predictor. The alternative is using dynamic dispatch which usually is pretty bad for performance.

This slightly changes the current behavior with RDF/XML, where it would just ignore anything aside from the default graph – this does not happen with NT/Turtle! Now all triple-only formats will throw a proper error when you try to do that. That behavior was introduced originally by Jena, not us.

Copy link
Collaborator

@Karolina-Bogacka Karolina-Bogacka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes complete sense as a new feature, looking at it I'm now kind of surprised that we did not have that before

@Karolina-Bogacka Karolina-Bogacka merged commit d97e3f0 into main Feb 1, 2026
8 checks passed
@Karolina-Bogacka Karolina-Bogacka deleted the GH-253/merge-graphs branch February 1, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants