digitalmars.D.bugs - [Issue 4151] New: Add weak references to Phobos/druntime
- d-bugmail puremagic.com (23/23) May 02 2010 http://d.puremagic.com/issues/show_bug.cgi?id=4151
- d-bugmail puremagic.com (9/9) Jan 06 2011 http://d.puremagic.com/issues/show_bug.cgi?id=4151
- d-bugmail puremagic.com (10/10) Jan 06 2011 http://d.puremagic.com/issues/show_bug.cgi?id=4151
- d-bugmail puremagic.com (12/12) Mar 16 2013 http://d.puremagic.com/issues/show_bug.cgi?id=4151
- d-bugmail puremagic.com (7/7) Oct 08 2013 http://d.puremagic.com/issues/show_bug.cgi?id=4151
- d-bugmail puremagic.com (7/7) Oct 16 2013 http://d.puremagic.com/issues/show_bug.cgi?id=4151
http://d.puremagic.com/issues/show_bug.cgi?id=4151 Summary: Add weak references to Phobos/druntime Product: D Version: future Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Phobos AssignedTo: nobody puremagic.com ReportedBy: nfxjfg gmail.com Just that. The Java API documentation may provide a good starting point as to what weak references should be able to do: http://java.sun.com/javase/7/docs/api/java/lang/ref/WeakReference.html Note that finalizers and the "hidden" rt_attach.../detach... functions are highly unsafe and hard to get right. As an example what can go wrong if users try to implement their own weak references, see bug 4150. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
May 02 2010
http://d.puremagic.com/issues/show_bug.cgi?id=4151 nfxjfg gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Jan 06 2011
http://d.puremagic.com/issues/show_bug.cgi?id=4151 Brad Roberts <braddr puremagic.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |braddr puremagic.com Resolution|INVALID | -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Jan 06 2011
http://d.puremagic.com/issues/show_bug.cgi?id=4151 Denis Shelomovskij <verylonglogin.reg gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |verylonglogin.reg gmail.com 15:06:59 MSK --- Even worse GC lock/unlock aren't parts of a druntime user API so one have to use ugly things like calling addRange/removeRange to ensure the memory will not be collected. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Mar 16 2013
http://d.puremagic.com/issues/show_bug.cgi?id=4151 13:58:32 MSD --- One can use this implementation for now: http://denis-sh.bitbucket.org/unstandard/unstd.memory.weakref.html -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Oct 08 2013
http://d.puremagic.com/issues/show_bug.cgi?id=4151 13:58:28 MSD --- A proposal to add library implementation without runtime changes: http://forum.dlang.org/thread/l3dj7b$2tvc$1 digitalmars.com -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Oct 16 2013