D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 11076 - Allow delete null in the spec
Summary: Allow delete null in the spec
Status: RESOLVED WONTFIX
Alias: None
Product: D
Classification: Unclassified
Component: druntime (show other issues)
Version: D1 (retired)
Hardware: All All
: P2 minor
Assignee: No Owner
URL:
Keywords: spec
Depends on:
Blocks:
 
Reported: 2013-09-20 12:27 UTC by David Eckardt
Modified: 2020-01-16 14:05 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description David Eckardt 2013-09-20 12:27:42 UTC 
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 Andrej Mitrovic 2013-09-20 16:30:39 UTC 
delete is going away, I wouldn't bother documenting this at all.
Comment 2 Andrej Mitrovic 2013-09-20 16:31:28 UTC 
(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 Stanislav Blinov 2018-11-24 09:11:37 UTC 
It's mentioned in passing in documentation of custom allocators: https://digitalmars.com/d/1.0/memory.html#newdelete

Maybe close this?
Comment 4 Mathias LANG 2020-01-16 14:05:34 UTC 
delete is going away, and D1 is (finally) dead too.