Issues · tc39/proposal-weakrefs · GitHub

This repository was archived by the owner on Jan 25, 2022. It is now read-only.

Labels Milestones

Q: Why not to add `getKeys() : array` instead?

#217

· c-smile opened

on Mar 24, 2021

Iterable WeakMap implementation in README is incorrect?

#213

· benjamingr opened

on Nov 3, 2020

Document expectations of WeakRef behavior in practice

#192

· tjcrowder opened

on Mar 3, 2020

Add API summary to README.md

#170

· cpcallen opened

on Nov 18, 2019

Consider not adding this as a feature.

#154

· wolfbeast opened

on Jul 10, 2019

Should finalizers be able to hint how much memory may be freed when they run?

follow-on proposal

#87

· wingo opened

on Apr 29, 2019

HTML job queue integration

host environment

#61

· littledan opened

on Feb 10, 2019

Documentation

#58

· littledan opened

on Jan 11, 2019

FAQ: Why not just add a callback to WeakMap/WeakSet?

#53

· xaviergonz opened

on Dec 2, 2018

Document the implications of the absense of a same-Realm check for WeakRefs

#52

· marjakh opened

on Nov 20, 2018

Needs discussion / clarification: if cleanup doesn't iterate all weak cells, when will it be called again?

#34

· marjakh opened

on Oct 17, 2018

Interesting impact on other specifications

#31

· domenic opened

on Jun 18, 2018