docs: add section about usage in sync execution #5
Conversation
This file contains 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
|
Thank you for the PR! I haven't merged it yet just because I assume we will probably update this once we figure out if clearKeptObjects() + FinalizationRegistry.cleanupSome() will work (and perhaps refer to using that). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Writing docs is hard, but I did want to follow up on our chat in "GC behaviour in sync execution" issue and do my best
I did want to code snippet to be abstract, but reading it now make it look weird (especially in context of "just"
weak-lru-cache, as what I did somewhat approximate its usage withlmdb-jsespecially with setting the cache if there was cache miss)Rendered version https://github.com/pieh/weak-lru-cache/blob/docs/sync-execution/README.md#usage-in-synchronous-execution
I did "Allow edits by maintainers" in case you want to make changes directly and avoid back and forth, but we can do back and forth too :)
Closes #4