Jesse Wright

@josd Turns out it does work on the 10^6 dataset if we use a production environment and increase the memory allocation for node to 8GB ``` jeswr@debian:~/jst/N3.js$ NODE_ENV=production node --max-old-space-size=8192...

> Does this already take into account the asynciterator changes Yes - that said I was doing it in a very 'hacky' manner of copy/pasting that unreleased locally since I...

> would you be able to profile one of those test runs Is something like this what you were thinking @jacoscaz (also be aware that the time scale is logarithmic)...

@RubenVerborgh - I think this is getting close to being ready for review - and whilst I think it can be further cleaned up in the future, I don't know...

> May I suggest to implement this in a separate class? Perhaps this is overcomplicating it - but if I go down that track is it worth trying it implement...

I've pushed the RDFJS implementation agnostic to https://github.com/jesse-wright-reasoning-honours/rdfjs-reasoner/blob/master/reasoner.ts. This is neither tied to n3 nor Comunica. Happy to clean up and move this repo to the `rdfjs/` organisation - in...

> how's perf @RubenVerborgh It ranges between 2-4x slower in the RDFJS version ``` Reasoning over TimBL profile and FOAF loading foaf ontology: 13.229ms loading tim berners lee profile card:...

> allternative approach could be to store this id value within the RDF/JS Term My main concern with this approach would be having to handle conflicting ID's if there are...

I'd be inclined to say that `readQuads` should be reserved as an internal property and not exposed in the typings. Do you have a use case for it that cannot...

Mainly just to leave the option of changing its behaviour in the future - for instance in work on https://github.com/rdfjs/N3.js/issues/281 or https://github.com/comunica/comunica/issues/594#issuecomment-1099889243, though such issues may not require changes to...