← Back to index | Original Bugzilla link

Bug 11076 – Allow delete null in the spec

Status
RESOLVED
Resolution
WONTFIX
Severity
minor
Priority
P2
Component
druntime
Product
D
Version
D1 (retired)
Platform
All
OS
All
Creation time
2013-09-20T12:27:42Z
Last change time
2020-01-16T14:05:34Z
Keywords
spec
Assigned to
No Owner
Creator
David Eckardt

Comments

Comment #0 by david.eckardt — 2013-09-20T12:27:42Z
In practice "delete null" has the defined behavior of a no-op, just like free(null), but this isn't mentioned in the language specification.
Comment #1 by andrej.mitrovich — 2013-09-20T16:30:39Z
delete is going away, I wouldn't bother documenting this at all.
Comment #2 by andrej.mitrovich — 2013-09-20T16:31:28Z
(In reply to comment #1) > delete is going away, I wouldn't bother documenting this at all. Well I see you've labeled this as D1 & D2, I've removed the D2 label, as delete is only going away in D2.
Comment #3 by stanislav.blinov — 2018-11-24T09:11:37Z
It's mentioned in passing in documentation of custom allocators: https://digitalmars.com/d/1.0/memory.html#newdelete Maybe close this?
Comment #4 by pro.mathias.lang — 2020-01-16T14:05:34Z
delete is going away, and D1 is (finally) dead too.