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

Should all calls really be cached? #29

Open
spalger opened this issue Aug 8, 2022 · 0 comments
Open

Should all calls really be cached? #29

spalger opened this issue Aug 8, 2022 · 0 comments

Comments

@spalger
Copy link

spalger commented Aug 8, 2022

I don't have any data to suggest this is a real problem, but when I see a cache that I can't control, clear, or avoid in the module scope of a library I smell potential uncontrollable memory issues and I really wish this library didn't cache results. It feels totally logical that the cache will only explode in very edge cases, but I think the same logic implies that people likely won't benefit much from this cache so I'd prefer if it was opt-in or just left for consumer to implement.

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

No branches or pull requests

1 participant