[Issue 2306] Scope for dynamic arrays should free memory.

2019-08-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=2306

RazvanN  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||razvan.nitu1...@gmail.com
 Resolution|--- |WONTFIX

--- Comment #12 from RazvanN  ---
D1 is not maintained anymore and now we have a library solution for scope
classes in std.typecons.scoped.

--


[Issue 2306] Scope for dynamic arrays should free memory.

2010-08-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306


David Simcha dsim...@yahoo.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX


--- Comment #7 from David Simcha dsim...@yahoo.com 2010-08-11 14:16:06 PDT ---
I'm closing this since we're doing away with scope classes and moving them to a
library solution.  The corresponding library solution for arrays is
std.container.Array.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 2306] Scope for dynamic arrays should free memory.

2010-08-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306


nfx...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||nfx...@gmail.com
Version|2.018   |D1
 Resolution|WONTFIX |
 OS/Version|Windows |All
   Severity|minor   |enhancement


--- Comment #8 from nfx...@gmail.com 2010-08-11 14:25:52 PDT ---
Still valid for D1.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 2306] Scope for dynamic arrays should free memory.

2010-08-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306


bearophile_h...@eml.cc changed:

   What|Removed |Added

 CC||bearophile_h...@eml.cc


--- Comment #9 from bearophile_h...@eml.cc 2010-08-11 14:52:54 PDT ---
I think D1 is feature-frozen, I don't think this will be ever added by Walter.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 2306] Scope for dynamic arrays should free memory.

2010-08-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306


Leandro Lucarella llu...@gmail.com changed:

   What|Removed |Added

 CC||llu...@gmail.com


--- Comment #10 from Leandro Lucarella llu...@gmail.com 2010-08-11 15:13:28 
PDT ---
(In reply to comment #9)
 I think D1 is feature-frozen, I don't think this will be ever added by Walter.

But this is not a feature request, is a bug report.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 2306] Scope for dynamic arrays should free memory.

2010-08-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306



--- Comment #11 from nfx...@gmail.com 2010-08-11 15:21:37 PDT ---
Nobody knows whether this is a bug report or an enhancement request because D1
is too underspecified.

Walter has added features to D1 in the past, although I suspect he's keeping
that low to advertise D2.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 2306] Scope for dynamic arrays should free memory.

2008-12-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306





--- Comment #5 from [EMAIL PROTECTED]  2008-12-11 06:25 ---
(In reply to comment #0)
 void test() {
 scope uint[] foo = new uint[100_000_000];
 }
 void test() {
 uint[] foo = new uint[100_000_000];
 scope(exit) delete foo;
 }
 
 This isn't a very serious bug, since there's an obvious, simple workaround, 
 but
 it's still an inconsistency in the language design, and ideally should be
 fixed.
 

consider this
-
void test() {
scope uint[] foo = new uint[100_000_000];
scope uint[] foo1 = foo;
}
-
how much should it free?


-- 



[Issue 2306] Scope for dynamic arrays should free memory.

2008-12-11 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=2306





--- Comment #6 from dsim...@yahoo.com  2008-12-11 22:54 ---
(In reply to comment #5)
 
 consider this
 -
 void test() {
 scope uint[] foo = new uint[100_000_000];
 scope uint[] foo1 = foo;
 }
 -
 how much should it free?
 

I guess this is where the T[new] and T[] types that have been proposed come in.
 foo would be T[new] so it would determine the freeing stuff. foo1 would be
T[], so it wouldn't.


--