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

store only locations, not string values #362

Open
bartveneman opened this issue Nov 6, 2023 · 0 comments
Open

store only locations, not string values #362

bartveneman opened this issue Nov 6, 2023 · 0 comments
Labels
🚨 breaking change changes that require a major version bump
Milestone

Comments

@bartveneman
Copy link
Member

I can think of two major use cases where I think it's most useful to no longer include substrings as aprt of the result:

The reason we don't need or even want to have the strings is that we can always get them on demand when we need them. For the webpage for example, we can get the string values only for the items we are rendering on screen and leave out the rest. This will lead to a messive memory reduction, making analysis and displaying a bunch faster.

@bartveneman bartveneman added the 🚨 breaking change changes that require a major version bump label Nov 6, 2023
@bartveneman bartveneman added this to the v6 milestone Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 breaking change changes that require a major version bump
Development

No branches or pull requests

1 participant