D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 14171 - Mark non-allocating GC functions as @nogc
Summary: Mark non-allocating GC functions as @nogc
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: druntime (show other issues)
Version: D2
Hardware: All All
: P1 normal
Assignee: No Owner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-12 03:00 UTC by weaselcat
Modified: 2018-05-11 01:46 UTC (History)
1 user (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 weaselcat 2015-02-12 03:00:25 UTC 
Many functions in the GC don't actually allocate, but are useful for building tools that help facilitate working around the GC - i.e, AddRange is vital for manually managed memory that holds references to GC allocated memory. I don't think there's a reason these shouldn't be @nogc but I could easily be wrong.