[Issue 11240] assumeSafeAppend could implicitly break immutablity

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=11240



--- Comment #4 from Jonathan M Davis <jmdavisProg at gmx.com> 2013-10-13 01:44:11 PDT ---
I think that making it so that assumeSafeAppend didn't work with const or
immutable would be akin to making free not work with const or immutable. Both
function are inherently unsafe and must be used correctly and could cause
serious issues if misused, and both are related to indicating which memory can
be used. But both are also just fine if used correctly. The key thing is in
making sure that it's clear in the documentation how the function is intented
to be used and that using it differently is unsafe.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------