Conversation
Member
Author
|
For reference, there is also a partial effort here #357 |
TimoKramer
force-pushed
the
main
branch
6 times, most recently
from
15ca402 to
6149e16
Compare
Member
Author
|
This is now covered in a better way with #748. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #206. First phase is going to be to make Datahike compile with cljs support in-memory. Compared to https://github.com/replikativ/datahike/tree/206-cljs-support this does not require a complete move to core.async yet, but will allow synchronizing indices between clojure and clojurescript peers, e.g. with replikativ. In the second phase we can then port Datahike to support both asynchronous and synchronous execution.