Giters
tc39
/
proposal-collection-normalization
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
39
Watchers:
21
Issues:
19
Forks:
8
tc39/proposal-collection-normalization Issues
Understanding the underlying problem better
Updated
3 years ago
Comments count
2
Path to Stage 3
Updated
3 years ago
Comments count
10
rename hooks
Updated
3 years ago
Comments count
14
should these be put under a namespace in the options object?
Closed
3 years ago
Comments count
2
Set of elements with custom equality
Closed
3 years ago
Comments count
1
Performance overhead?
Closed
3 years ago
Comments count
2
Use within WebIDL?
Updated
4 years ago
Comments count
1
should hooks be called with `this` set to the object they are pulled from?
Closed
5 years ago
Comments count
10
Gather use cases for Map {toValue}
Closed
5 years ago
Comments count
5
Gather language information on naming of items within a Set
Closed
5 years ago
Comments count
2
Should compositeKey be in a module
Closed
5 years ago
Comments count
21
Yes Please!
Closed
5 years ago
Comments count
1
Also "revalue" for maps?
Closed
5 years ago
Comments count
2
Bikeshed: "rekey" naming
Closed
5 years ago
Comments count
6
Sets do not have keys, they have values
Closed
5 years ago
Comments count
1
What happens when iterating over a rekeyed Map?
Closed
5 years ago
Comments count
14
Key and value validation/normalization use case
Closed
5 years ago
Comments count
3
Does toValue change what's stored in the Set?
Closed
5 years ago
Comments count
7
toValue for Map?
Closed
5 years ago
Comments count
3