Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Issues: tc39/proposal-weakrefs

12 Open 100 Closed
12 Open 100 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Q: Why not to add getKeys() : array instead?
#217 opened Mar 24, 2021 by c-smile
5
Iterable WeakMap implementation in README is incorrect?
#213 opened Nov 3, 2020 by benjamingr
1
Document expectations of WeakRef behavior in practice documentation
#192 opened Mar 3, 2020 by tjcrowder
3
Add API summary to README.md documentation
#170 opened Nov 18, 2019 by cpcallen
2
Consider not adding this as a feature.
#154 opened Jul 10, 2019 by wolfbeast
9
Should finalizers be able to hint how much memory may be freed when they run? follow-on proposal
#87 opened Apr 29, 2019 by wingo
18
HTML job queue integration host environment
#61 opened Feb 10, 2019 by littledan
2
Documentation documentation
#58 opened Jan 11, 2019 by littledan
2
FAQ: Why not just add a callback to WeakMap/WeakSet? documentation
#53 opened Dec 2, 2018 by xaviergonz
6
Document the implications of the absense of a same-Realm check for WeakRefs documentation
#52 opened Nov 20, 2018 by marjakh
7
Needs discussion / clarification: if cleanup doesn't iterate all weak cells, when will it be called again? documentation
#34 opened Oct 17, 2018 by marjakh
25
Interesting impact on other specifications documentation
#31 opened Jun 18, 2018 by domenic
1
5
ProTip! Add no:assignee to see everything that’s not assigned.