Bug 6151 – [GC] Make the GC functions weakly pure

Original discussion: * http://www.digitalmars.com/d/archives/digitalmars/D/Should_GC.malloc_be_considered_pure_137919.html * http://www.digitalmars.com/d/archives/digitalmars/D/Re_Should_GC.malloc_be_considered_pure_137984.html * http://www.digitalmars.com/d/archives/digitalmars/D/Re_Should_GC.malloc_be_considered_pure_138177.html Due to practicality, allocation is allowed in pure function. By the same token, GC.malloc should also be 'pure'. GC functions being not weakly-pure is the reason why std.conv.to (bug 4850) and std.array.appender cannot be pure. Marking the GC functions are pure are easy, but the problem is the implication behind it. Technically, GC functions depend on global states, so they cannot be weakly pure. But then std.array.appender can never become pure without sacrificing performance.

What we really need in order to move forward with this is a way to explicitly tell the compiler that something is weakly pure.

This seems solved to me. Since a couple of releases, AFAIK. Close WORKSFORME?

We still have https://issues.dlang.org/show_bug.cgi?id=15862. But we can close this.