You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: