Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor/db protocol implementations #844

Merged
merged 11 commits into from
Jul 18, 2024

Conversation

zonotope
Copy link
Contributor

This patch is the second in a series of replacements for #789 that cleans up some of the FlakeDB protocol implementations (more work to be done on that front later) and adds a new protocol for reasoning. The reasoning api functions currently in main operate on a FlakeDB directly, so they would break if they were ever called on an AsyncDB.

@zonotope zonotope requested a review from a team July 18, 2024 18:42
Copy link
Contributor

@dpetran dpetran left a comment

Choose a reason for hiding this comment

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

👍

This avoids two nested calls to `satisfies?` which is slower than the calls to
`map?` and `sequential?` that replaces it.
This reverts commit dbc931e. This commit
doesn't work because `map?` returns true for clojure records, which all database
instances are. I don't think the calls to `satisfies?` can be avoided
unfortunately.
@zonotope zonotope merged commit 6bfc29a into main Jul 18, 2024
7 checks passed
@zonotope zonotope deleted the refactor/db-protocol-implementations branch July 18, 2024 23:32
@zonotope zonotope mentioned this pull request Jul 19, 2024
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.

2 participants