immutable-tuple
immutable-tuple copied to clipboard
benjamn
Immutable finite list objects with constant-time equality testing (===) and no memory leaks.
As per the README > Astute readers may object that some bookkeeping data remains in memory when you create tuple objects with prefixes of primitive values This can be solved...
In JavaScript `Map` and `Set` do not distinguish `0` and `-0` as different keys, instead `-0` is normalized to `0`. This leads to the following 'bug': ```js const { tuple...
The description claims "no leaks", but if you do `Tuple(primitive)`, that creates a `UniversalWeakMap` which can never be garbage collected. If you're creating a lot of tuples with a lot...
Hi! UniversalWeakMap can be useful on its own, a good replacement for [primitive-pool](https://ghub.io/primitive-pool). Can that possibly be exported as a separate entry? ```js import { UniversalWeakMap } from 'immutable-tuple' ```
To store primitive keys in WeakMap, the [primitive-pool](https://github.com/dy/primitive-pool) or similar technique can be used. @benjamn (just an idea for alternative solution)
Hi Ben, I don't get this error in React Native iOS or Android, but I do in Chrome with [react-native-web](https://github.com/necolas/react-native-web). I don't know whether it's something you can publish an...
