fix: replace persistent term usage with ets table#22
Merged
tsloughter merged 1 commit intomainfrom Dec 8, 2025
Merged
Conversation
tsloughter
force-pushed
the
pterm-to-ets
branch
from
969f2b7 to
614c712
Compare
Types are stored in a public ets table instead of in the persistent terms. It feels safer since types could be updated and pterm can get slower with more elements in it so forcing the user to already have a bunch of terms in it just for this seems like a misuse.
tsloughter
force-pushed
the
pterm-to-ets
branch
from
614c712 to
f0b7c9f
Compare
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.
Types are stored in a public ets table instead of in the persistent terms. It feels safer since types could be updated and pterm can get slower with more elements in it so forcing the user to already have a bunch of terms in it just for this seems like a misuse.