Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We don't do this right now - optimising for incremental changes is actually better done by maintaining forward-chaining inferences (like the OP) rather than backward chaining, and then invalidating and updating just the inferences that have modified dependencies. Which you want depends on use case often: if you have often changing data backward chaining is generally better, but if it's largely static you can get large performance wins by materialising all the inferences, once, via forward-chaining.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: