https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #31 from github-bugzi...@puremagic.com ---
Commit pushed to 2.067 at https://github.com/D-Programming-Language/druntime
https://github.com/D-Programming-Language/druntime/commit/dbbea7c5bd4d8936dc8cb523b65f771842f2a487
Merge pull request
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #30 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/D-Programming-Language/druntime
https://github.com/D-Programming-Language/druntime/commit/dbbea7c5bd4d8936dc8cb523b65f771842f2a487
Merge pull request
https://issues.dlang.org/show_bug.cgi?id=2834
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #28 from Orvid King blah38...@gmail.com ---
Where should I add it? It can't be in rt.lifetime, because that's not exposed
to the user.
--
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #29 from Andrei Alexandrescu and...@erdani.com ---
core.memory?
--
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #27 from Andrei Alexandrescu and...@erdani.com ---
Could you please add a function to druntime callStructDtorsDuringGC(bool)? That
would give a chance people who have issues with the called destructors to
revert back to the old behavior
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #25 from Orvid King blah38...@gmail.com ---
Fine by me.
--
https://issues.dlang.org/show_bug.cgi?id=2834
hst...@quickfur.ath.cx changed:
What|Removed |Added
CC||hst...@quickfur.ath.cx
--- Comment
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #23 from Orvid King blah38...@gmail.com ---
And another update.
The fix to the other issue that this encountered has already been merged, and
the main DRuntime PR has been running green on the autotester for a while now.
It's just
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #24 from Andrei Alexandrescu and...@erdani.com ---
Ready to take the big step with 2.067?
--
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #22 from Orvid King blah38...@gmail.com ---
Ok, so, to give an update on this issue, I've now implemented the invoking of
destructors on heap allocated structs, as well as arrays of structs. It
required a fix to a bug in DMD with the
https://issues.dlang.org/show_bug.cgi?id=2834
Dmitry Olshansky dmitry.o...@gmail.com changed:
What|Removed |Added
CC||dmitry.o...@gmail.com
https://issues.dlang.org/show_bug.cgi?id=2834
Rainer Schuetze r.sagita...@gmx.de changed:
What|Removed |Added
CC||r.sagita...@gmx.de
---
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #15 from Orvid King blah38...@gmail.com ---
Would making all the writeln's in http://dpaste.dzfl.pl/fbb4a15cda14 print out
be an acceptable solution to this issue? (that is, making heap-allocated
structs call their destructors)
--
https://issues.dlang.org/show_bug.cgi?id=2834
David Nadlinger c...@klickverbot.at changed:
What|Removed |Added
CC||c...@klickverbot.at
---
https://issues.dlang.org/show_bug.cgi?id=2834
Orvid King blah38...@gmail.com changed:
What|Removed |Added
CC||blah38...@gmail.com
---
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #18 from Jonathan M Davis jmdavisp...@gmx.com ---
(In reply to Orvid King from comment #17)
https://github.com/D-Programming-Language/druntime/pull/864
It's not feasibly possible to call destructors on heap-allocated arrays of
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #19 from Orvid King blah38...@gmail.com ---
We still wouldn't be able to call the destructors in structs for arrays even
with precise heap scanning, because we can't know that each value in the array
is actually valid. Take for instance
https://issues.dlang.org/show_bug.cgi?id=2834
Benoit Rostykus benoit.rosty...@adroll.com changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=2834
Jonathan M Davis jmdavisp...@gmx.com changed:
What|Removed |Added
CC||jmdavisp...@gmx.com
https://issues.dlang.org/show_bug.cgi?id=2834
--- Comment #14 from Jonathan M Davis jmdavisp...@gmx.com ---
(In reply to Benoit Rostykus from comment #12)
AdRoll (the company I work for) just put a $1000 bounty on this bug:
That's quite the bounty.
--
https://d.puremagic.com/issues/show_bug.cgi?id=2834
Dicebot pub...@dicebot.lv changed:
What|Removed |Added
CC||pub...@dicebot.lv
https://d.puremagic.com/issues/show_bug.cgi?id=2834
rswhi...@googlemail.com changed:
What|Removed |Added
CC||rswhi...@googlemail.com
---
On 11/21/2010 08:20 PM, Sean Kelly wrote:
d-bugm...@puremagic.com wrote:
http://d.puremagic.com/issues/show_bug.cgi?id=2834
Max Samukhasamu...@voliacable.com changed:
What|Removed |Added
d-bugm...@puremagic.com wrote:
http://d.puremagic.com/issues/show_bug.cgi?id=2834
Max Samukha samu...@voliacable.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=2834
Max Samukha samu...@voliacable.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=2834
--- Comment #9 from Max Samukha samu...@voliacable.com 2010-11-18 03:59:12
PST ---
(In reply to comment #8)
We have a nasty problem when destructors are called on the appended elements
because postblits was not run for them during append.
I
http://d.puremagic.com/issues/show_bug.cgi?id=2834
bearophile_h...@eml.cc changed:
What|Removed |Added
CC||bearophile_h...@eml.cc
---
http://d.puremagic.com/issues/show_bug.cgi?id=2834
--- Comment #7 from bearophile_h...@eml.cc 2010-07-11 17:24:58 PDT ---
One case where struct destructors are not called, in this situation it seems
simpler for the GC to know what destructors to call:
import core.memory: GC;
import
http://d.puremagic.com/issues/show_bug.cgi?id=2834
Rob Jacques sandf...@jhu.edu changed:
What|Removed |Added
CC||and...@metalanguage.com
http://d.puremagic.com/issues/show_bug.cgi?id=2834
Sean Kelly s...@invisibleduck.org changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=2834
--- Comment #5 from Sean Kelly s...@invisibleduck.org 2010-07-10 08:41:54 PDT
---
Fixing this will probably be fairly involved. The GC will have to store a
TypeInfo reference for each block that needs to be finalized. The best
approach may
32 matches
Mail list logo
