tc39 proposal-collection-normalization issues - Githubissues

tc39 / proposal-collection-normalization

MIT License

41 stars 8 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Understanding the underlying problem better

#21 codehag opened 3 years ago
2
Path to Stage 3

#20 bmeck opened 3 years ago
10
Use within WebIDL?

#19 dead-claudia opened 4 years ago
1
Set of elements with custom equality

#18 bergus closed 3 years ago
1
Performance overhead?

#17 rkatic closed 3 years ago
2
typos

#16 caub closed 3 years ago
0
should hooks be called with `this` set to the object they are pulled from?

#15 bmeck closed 5 years ago
10
should these be put under a namespace in the options object?

#14 bmeck closed 3 years ago
2
rename hooks

#13 bmeck opened 5 years ago
14
docs: fix typo

#12 Jason-Cooke closed 5 years ago
0
Gather use cases for Map {toValue}

#1 bmeck closed 5 years ago
5
Gather language information on naming of items within a Set

#2 bmeck closed 5 years ago
2
toValue for Map?

#4 ljharb closed 5 years ago
3
Does toValue change what's stored in the Set?

#5 ljharb closed 5 years ago
7
Key and value validation/normalization use case

#6 domenic closed 5 years ago
3
What happens when iterating over a rekeyed Map?

#7 zenparsing closed 5 years ago
14
Sets do not have keys, they have values

#8 domenic closed 5 years ago
1
Bikeshed: "rekey" naming

#9 domenic closed 5 years ago
6
Also "revalue" for maps?

#10 domenic closed 5 years ago
2
Yes Please!

#11 benjamingr closed 5 years ago
1
Should compositeKey be in a module

#3 bmeck closed 5 years ago
21