Why does #every return false on the empty store

[jeswr]

As shown in the test here #every returns false when called on an empty store. There is a test enforcing this behavior at

N3.js/test/N3Store-test.js

Line 92 in 0ba9ec2

expect(store.every(alwaysTrue, null, null, null, null)).toBe(false);

This does not align with set semantics where #every would align with forAll and thus be vacuously true on the empty set.

It also goes against the RDF/JS Dataset definition of for #every https://rdf.js.org/dataset-spec/#dom-dataset-every; and so in order to complete #288 we would need to alter this behavior and decide whether this change is (1) breaking or (2) a bug fix - despite the fact that there is a test enforcing the buggy behavior. @RubenVerborgh what do you think?

[RubenVerborgh]

Oops; let's treat as a bug fix. The test is wrong indeed.

[github-actions]

🎉 This issue has been resolved in version 1.19.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀