[Issue 4621] Destructors are inherently un-@safe

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4621 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 4621] Destructors are inherently un-@safe

2016-10-18 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4621 anonymous4 changed: What|Removed |Added See Also|

[Issue 4621] Destructors are inherently un-@safe

2016-09-29 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4621 anonymous4 changed: What|Removed |Added Keywords||spec --

[Issue 4621] Destructors are inherently un-@safe

2016-09-29 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4621 anonymous4 changed: What|Removed |Added Keywords||safe

[Issue 4621] Destructors are inherently un-@safe

2013-08-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=4621 Maxim Fomin ma...@maxim-fomin.ru changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 4621] Destructors are inherently un-@safe

2013-08-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=4621 --- Comment #19 from Michel Fortin michel.for...@michelf.com 2013-08-05 17:13:32 EDT --- (In reply to comment #18) This is invalid report since @safe has nothing to do with accessing pointers/references which turned out to be nulls. Maxim,