Difference between revisions of "Stuff in Phobos That Generates Garbage"

From D Wiki
Jump to: navigation, search
(Comment std.uuid)
Line 9,089: Line 9,089:
 
|parseUUID
 
|parseUUID
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L1182 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L1182 std.uuid]
 
|parseUUID
 
|parseUUID
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L1190 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L1190 std.uuid]
 
|parseUUID
 
|parseUUID
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L335 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L335 std.uuid]
 
|****
 
|****
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L340 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L340 std.uuid]
 
|****
 
|****
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L353 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L353 std.uuid]
 
|****
 
|****
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L371 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L371 std.uuid]
 
|****
 
|****
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L382 std.uuid]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/uuid.d#L382 std.uuid]
 
|****
 
|****
 
|'new' causes GC allocation
 
|'new' causes GC allocation
−
| ???
+
| throws Exception
 
|-
 
|-
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/variant.d#L1387 std.variant]
 
|[https://github.com/D-Programming-Language//phobos/blob/d4d98124ab6cbef7097025a7cfd1161d1963c87e/std/variant.d#L1387 std.variant]

Revision as of 10:03, 9 October 2014

Auto-generated results as reported by compiler (building unittests with -vgc flag of DMD).

For templates only code that is _instantiated_ by unittests build is accounted for (~ all covered code).

The tool used to post-process the output can be found here.

(Note: Artifact column has auto-assigned name on best-effort basis and may be completely wrong)

Module Artifact Reason Possible Fix(es)
std.algorithm TimSortImpl.sort setting 'length' may cause GC allocation This sets the length only if (__ctfe). Would it be difficult to have the compiler detect CTFE-only code and not reject it?
std.algorithm TimSortImpl.ensureCapacity setting 'length' may cause GC allocation Same here, this is CTFE only.
std.algorithm reduce.reduceImpl 'new' causes GC allocation This is a throw when empty range and no seed.
std.algorithm makeIndex operator ~ may cause GC allocation Throws (via enforce) if the index integral type cannot fit the number of elements in the range. Even before throwing it uses concatenation to build the error message.
std.algorithm topNIndex using closure causes GC allocation CL1
std.algorithm largestPartialIntersectionWeighted using closure causes GC allocation CL1
std.algorithm ror indexing an associative array may cause GC allocation ???
std.algorithm castSwitch 'new' causes GC allocation Throws a new SwitchError if no choice matches or a void choice is executed and not all choices are void.
std.algorithm castSwitch 'new' causes GC allocation Throws a new SwitchError if no choice matches or a void choice is executed and not all choices are void.
std.algorithm castSwitch 'new' causes GC allocation Throws a new SwitchError if no choice matches or a void choice is executed and not all choices are void.
std.algorithm castSwitch 'new' causes GC allocation Throws a new SwitchError if no choice matches or a void choice is executed and not all choices are void.
std.algorithm cartesianProduct using closure causes GC allocation CL2
std.algorithm predSwitch 'new' causes GC allocation Throws a new SwitchError if no default return expression and predicate is false for all expressions.

Throws a new SwitchError if a void return expression is executed without throwing anything.

std.algorithm predSwitch 'new' causes GC allocation Throws a new SwitchError if no default return expression and predicate is false for all expressions.

Throws a new SwitchError if a void return expression is executed without throwing anything.

std.algorithm SplitterResult.front 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm SplitterResult.popFront 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm splitter 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm splitter 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm ignored indexing an associative array may cause GC allocation ???
std.algorithm ignored 'new' causes GC allocation ???
std.algorithm commonPrefix 'new' causes GC allocation ???
std.algorithm Levenshtein.path operator ~= may cause GC allocation ???
std.algorithm Levenshtein.path operator ~= may cause GC allocation ???
std.algorithm Levenshtein.path operator ~= may cause GC allocation ???
std.algorithm Levenshtein.AllocMatrix 'delete' requires GC Deletes the current matrix if _matrix.length is less than requested size.
std.algorithm Levenshtein.AllocMatrix 'new' causes GC allocation Allocates an array of CostType if _matrix.length is less than requested size.
std.algorithm Cache.front 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm Cache.if 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm Cache.popFront 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.algorithm Cache.if 'new' causes GC allocation If version(assert) is defined this will throw a new RangeError for an empty range.
std.array insertInPlace setting 'length' may cause GC allocation ???
std.array insertInPlace setting 'length' may cause GC allocation ???
std.array replicate 'new' causes GC allocation ???
std.array split operator ~= may cause GC allocation ???
std.array split operator ~= may cause GC allocation ???
std.array replace 'new' causes GC allocation ???
std.array replaceInPlace operator ~ may cause GC allocation ???
std.array Appender.arr 'new' causes GC allocation ???
std.array Appender.arr setting 'length' may cause GC allocation ???
std.array Appender.ensureAddable 'new' causes GC allocation ???
std.array Appender.ensureAddable 'new' causes GC allocation ???
std.array Appender.ensureAddable setting 'length' may cause GC allocation ???
std.array Appender.ensureAddable operator ~= may cause GC allocation ???
std.array assocArray indexing an associative array may cause GC allocation ???
std.array array operator ~= may cause GC allocation ???
std.array arrayAllocImpl 'new' causes GC allocation ???
std.array arrayAllocImpl 'new' causes GC allocation ???
std.array arrayAllocImpl operator ~= may cause GC allocation ???
std.array arrayAllocImpl operator ~= may cause GC allocation ???
std.array arrayAllocImpl 'new' causes GC allocation ???
std.base64 Base64Impl.ubyte 'new' causes GC allocation ???
std.base64 Base64Impl.Decoder 'new' causes GC allocation ???
std.base64 Base64Impl.Decoder operator ~= may cause GC allocation ???
std.base64 Base64Impl.Decoder setting 'length' may cause GC allocation ???
std.base64 Base64Impl.Decoder 'new' causes GC allocation ???
std.base64 Base64Impl.Decoder 'new' causes GC allocation ???
std.base64 Base64Impl.Decoder 'new' causes GC allocation ???
std.base64 Base64Impl.Decoder 'new' causes GC allocation ???
std.base64 Base64Impl.int operator ~ may cause GC allocation ???
std.base64 Base64Impl.int 'new' causes GC allocation ???
std.base64 Base64Impl.int operator ~ may cause GC allocation ???
std.base64 Base64Impl.char 'new' causes GC allocation ???
std.base64 Base64Impl.Encoder 'new' causes GC allocation ???
std.base64 Base64Impl.Encoder setting 'length' may cause GC allocation ???
std.base64 Base64Impl.Encoder 'new' causes GC allocation ???
std.base64 Base64Impl.ubyte 'new' causes GC allocation ???
std.base64 Base64Impl.decode 'new' causes GC allocation ???
std.bigint BigInt.toString operator ~ may cause GC allocation ???
std.bigint BigInt.toString 'new' causes GC allocation ???
std.bigint BigInt.checkDivByZero 'new' causes GC allocation ???
std.bigint toDecimalString operator ~= may cause GC allocation ???
std.bigint toHex operator ~= may cause GC allocation ???
std.bitmanip BitArray.toString 'new' causes GC allocation ???
std.bitmanip BitArray.toString operator ~ may cause GC allocation ???
std.bitmanip BitArray.bitsSet using closure causes GC allocation CL2
std.bitmanip myToStringx operator ~ may cause GC allocation ???
std.bitmanip myToString operator ~ may cause GC allocation ???
std.bitmanip BitArray.length setting 'length' may cause GC allocation ???
std.complex Complex.toString operator ~= may cause GC allocation ???
std.complex Complex.toString using closure causes GC allocation CL3
std.complex Complex.toString operator ~= may cause GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency locate 'new' causes GC allocation ???
std.concurrency thisTid 'new' causes GC allocation ???
std.concurrency _spawn using closure causes GC allocation CL4
std.concurrency _spawn 'new' causes GC allocation ???
std.concurrency _spawn 'new' causes GC allocation ???
std.concurrency _spawn indexing an associative array may cause GC allocation ???
std.concurrency receiveOnly 'new' causes GC allocation ???
std.concurrency OnCrowding 'new' causes GC allocation ???
std.concurrency static 'new' causes GC allocation ???
std.concurrency register operator ~= may cause GC allocation ???
std.concurrency register indexing an associative array may cause GC allocation ???
std.concurrency register indexing an associative array may cause GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array the 'new' causes GC allocation ???
std.container.array a 'new' causes GC allocation ???
std.container.array to 'new' causes GC allocation ???
std.container.array to 'new' causes GC allocation ???
std.container.array operators 'new' causes GC allocation ???
std.container.dlist DList.createNode 'new' causes GC allocation ???
std.container.dlist DList.initialize 'new' causes GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl indexing an associative array may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse operator ~ may cause GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse 'new' causes GC allocation ???
std.conv parse operator ~= may cause GC allocation ???
std.conv parse indexing an associative array may cause GC allocation ???
std.conv parseEscape operator ~ may cause GC allocation ???
std.conv textImpl operator ~= may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv strippedOctalLiteral operator ~= may cause GC allocation ???
std.conv convError 'new' causes GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv convError 'new' causes GC allocation ???
std.conv parseError 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl operator ~ may cause GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.conv toImpl 'new' causes GC allocation ???
std.cstream ulong 'new' causes GC allocation ???
std.cstream din 'new' causes GC allocation ???
std.cstream dout 'new' causes GC allocation ???
std.cstream derr 'new' causes GC allocation ???
std.csv CsvReader.prime indexing an associative array may cause GC allocation ???
std.csv CsvReader.prime 'new' causes GC allocation ???
std.csv CsvReader.prime 'new' causes GC allocation ???
std.csv CsvRecord.popFront 'new' causes GC allocation ???
std.csv CsvRecord.popFront 'new' causes GC allocation ???
std.csv CsvRecord.prime 'new' causes GC allocation ???
std.csv CSVException.string operator ~ may cause GC allocation ???
std.csv CsvRecord.prime 'new' causes GC allocation ???
std.csv csvNextToken 'new' causes GC allocation ???
std.csv csvNextToken 'new' causes GC allocation ???
std.csv csvNextToken 'new' causes GC allocation ???
std.csv CsvReader.input 'new' causes GC allocation ???
std.csv CsvReader.input 'new' causes GC allocation ???
std.csv CsvReader.input indexing an associative array may cause GC allocation ???
std.csv CsvReader.input operator ~= may cause GC allocation ???
std.csv CsvReader.input setting 'length' may cause GC allocation ???
std.csv CsvReader.input indexing an associative array may cause GC allocation ???
std.csv CsvReader.input 'new' causes GC allocation ???
std.csv CsvReader.input operator ~ may cause GC allocation ???
std.csv CsvReader.input 'new' causes GC allocation ???
std.datetime Date.dayOfYear 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Date.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation ???
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime TimeOfDay.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromISOString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromISOExtString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime DateTime.fromSimpleString 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval's constructor 'new' causes GC allocation Throws a DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval's constructor 'new' causes GC allocation Throws a DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.begin 'new' causes GC allocation Throws a DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.end 'new' causes GC allocation Throws a DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.intersection 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.intersection 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.intersection 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.merge 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.merge 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.merge 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the error message wouldn't contain the bad input and would therefore be less informative.
std.datetime Interval.shift 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.shift 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval.expand 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception.
std.datetime Interval._enforceNotEmpty 'new' causes GC allocation Throws a new DateTimeException on bad input. This could be changed to a pre-allocated exception, but then the line number would not be in the correct spot, since it's essentially like enforce. A better approach would be to get rid of the function and then pre-allocate an exception for each place it was being called, but that would be pre-allocating several exceptions, since many of Interval's functions call it.
std.datetime SysTime.fracSecs 'new' causes GC allocation ???
std.datetime SysTime.fracSecs 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime SysTime.fracSec 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime delegate using closure causes GC allocation CL5
std.datetime delegate using closure causes GC allocation CL5
std.datetime delegate using closure causes GC allocation CL5
std.datetime delegate using closure causes GC allocation CL5
std.datetime IntervalRange._enforceNotEmpty 'new' causes GC allocation ???
std.datetime IntervalRange._enforceCorrectDirection 'new' causes GC allocation ???
std.datetime IntervalRange._enforceCorrectDirection 'new' causes GC allocation ???
std.datetime PosInfIntervalRange._enforceCorrectDirection 'new' causes GC allocation ???
std.datetime NegInfIntervalRange._enforceCorrectDirection 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime SimpleTimeZone.fromISOString 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** operator ~= may cause GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime **** 'new' causes GC allocation ???
std.datetime DosFileTimeToSysTime 'new' causes GC allocation ???
std.datetime DosFileTimeToSysTime 'new' causes GC allocation ???
std.datetime SysTimeToDosFileTime 'new' causes GC allocation ???
std.datetime SysTimeToDosFileTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime parseRFC822DateTime 'new' causes GC allocation ???
std.datetime enforceValid 'new' causes GC allocation ???
std.datetime enforceValid 'new' causes GC allocation ???
std.datetime enforceValid 'new' causes GC allocation ???
std.datetime enforceValid 'new' causes GC allocation ???
std.datetime enforceValid 'new' causes GC allocation ???
std.datetime monthFromString 'new' causes GC allocation ???
std.datetime fracSecsFromISOString 'new' causes GC allocation ???
std.datetime fracSecsFromISOString 'new' causes GC allocation ???
std.datetime fracSecsFromISOString 'new' causes GC allocation ???
std.datetime Clock.currStdTime 'new' causes GC allocation ???
std.datetime SysTime.DateTime 'new' causes GC allocation ???
std.datetime SysTime.DateTime 'new' causes GC allocation ???
std.datetime SysTime.DateTime 'new' causes GC allocation ???
std.datetime SysTime.toISOString operator ~ may cause GC allocation ???
std.datetime SysTime.toISOString operator ~ may cause GC allocation ???
std.datetime SysTime.toISOExtString operator ~ may cause GC allocation ???
std.datetime SysTime.toISOExtString operator ~ may cause GC allocation ???
std.datetime SysTime.toSimpleString operator ~ may cause GC allocation ???
std.datetime SysTime.toSimpleString operator ~ may cause GC allocation ???
std.datetime SysTime.fromISOString 'new' causes GC allocation ???
std.datetime SysTime.fromISOExtString 'new' causes GC allocation ???
std.datetime SysTime.fromISOExtString 'new' causes GC allocation ???
std.datetime SysTime.fromSimpleString 'new' causes GC allocation ???
std.datetime SysTime.fromSimpleString 'new' causes GC allocation ???
std.datetime Date.yearBC 'new' causes GC allocation ???
std.datetime Date.yearBC 'new' causes GC allocation ???
std.digest.digest ubyte 'new' causes GC allocation ???
std.encoding sanitize 'new' causes GC allocation ???
std.encoding transcode 'new' causes GC allocation ???
std.encoding transcode setting 'length' may cause GC allocation ???
std.encoding EncodingScheme.register operator ~ may cause GC allocation ???
std.encoding EncodingScheme.register 'new' causes GC allocation ???
std.encoding EncodingScheme.register indexing an associative array may cause GC allocation ???
std.encoding EncodingScheme.create operator ~ may cause GC allocation ???
std.encoding EncodingScheme.create 'new' causes GC allocation ???
std.encoding EncodingScheme.create operator ~ may cause GC allocation ???
std.encoding EncodingScheme.create 'new' causes GC allocation ???
std.encoding EncodingScheme.sanitize 'new' causes GC allocation ???
std.encoding EncodingSchemeASCII.const array literal may cause GC allocation ???
std.encoding EncodingSchemeLatin1.const array literal may cause GC allocation ???
std.encoding EncodingSchemeWindows1252.const array literal may cause GC allocation ???
std.encoding EncodingSchemeUtf8.const array literal may cause GC allocation ???
std.encoding EncodingSchemeUtf16Native.const array literal may cause GC allocation ???
std.encoding EncodingSchemeUtf32Native.const array literal may cause GC allocation ???
std.encoding EncoderFunctions.WriteToString() operator ~= may cause GC allocation ???
std.exception ErrnoException.msg operator ~ may cause GC allocation ???
std.exception assertThrown 'new' causes GC allocation ???
std.exception bailOut 'new' causes GC allocation ???
std.exception bailOut 'new' causes GC allocation ???
std.exception errnoEnforce 'new' causes GC allocation ???
std.exception enforceEx.enforceEx 'new' causes GC allocation ???
std.exception enforceEx.enforceEx 'new' causes GC allocation ???
std.exception assertNotThrown operator ~ may cause GC allocation ???
std.exception assertNotThrown 'new' causes GC allocation ???
std.exception assumeWontThrow operator ~ may cause GC allocation ???
std.exception assumeWontThrow 'new' causes GC allocation ???
std.exception assumeWontThrow operator ~ may cause GC allocation ???
std.exception assumeWontThrow 'new' causes GC allocation ???
std.exception assumeWontThrow operator ~ may cause GC allocation ???
std.file ensureDirExists 'new' causes GC allocation ???
std.file cenforce 'new' causes GC allocation ???
std.file rmdir 'new' causes GC allocation ???
std.file rmdir setting 'length' may cause GC allocation ???
std.file rmdir setting 'length' may cause GC allocation ???
std.file rmdir 'new' causes GC allocation ???
std.file **** 'new' causes GC allocation ???
std.file **** operator ~ may cause GC allocation ???
std.file **** operator ~ may cause GC allocation ???
std.file rmdirRecurse 'new' causes GC allocation ???
std.file read 'delete' requires GC ???
std.file dirEntries using closure causes GC allocation CL2
std.file remove operator ~ may cause GC allocation ???
std.file std operator ~ may cause GC allocation ???
std.format FormatSpec.fillUp 'new' causes GC allocation ???
std.format singleSpec 'new' causes GC allocation ???
std.format singleSpec 'new' causes GC allocation ???
std.format singleSpec 'new' causes GC allocation ???
std.format formatRange 'new' causes GC allocation ???
std.format formatNth operator ~= may cause GC allocation ???
std.format formatNth operator ~ may cause GC allocation ???
std.format formatNth operator ~ may cause GC allocation ???
std.format getNthInt 'new' causes GC allocation ???
std.format getNthInt 'new' causes GC allocation ???
std.format unformatRange operator ~= may cause GC allocation ???
std.format unformatRange indexing an associative array may cause GC allocation ???
std.format primitiveTypeInfo associative array literal may cause GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat operator ~ may cause GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format doFormat 'new' causes GC allocation ???
std.format FormatSpec.fillUp 'new' causes GC allocation ???
std.functional partial.if operator ~= may cause GC allocation ???
std.functional partial.if operator ~= may cause GC allocation ???
std.functional memoize.memoize indexing an associative array may cause GC allocation ???
std.getopt Option operator ~ may cause GC allocation ???
std.getopt Option operator ~ may cause GC allocation ???
std.getopt Option operator ~ may cause GC allocation ???
std.getopt getoptImpl operator ~= may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl operator ~ may cause GC allocation ???
std.getopt getoptImpl 'new' causes GC allocation ???
std.getopt getoptImpl operator ~= may cause GC allocation ???
std.getopt handleOption operator ~= may cause GC allocation ???
std.getopt handleOption operator ~= may cause GC allocation ???
std.getopt handleOption operator ~ may cause GC allocation ???
std.getopt handleOption operator ~ may cause GC allocation ???
std.getopt handleOption operator ~ may cause GC allocation ???
std.getopt handleOption operator ~ may cause GC allocation ???
std.getopt handleOption operator ~= may cause GC allocation ???
std.getopt handleOption operator ~= may cause GC allocation ???
std.getopt handleOption indexing an associative array may cause GC allocation ???
std.internal.math.biguintcore BigUint.immutable(BigDigit) array literal may cause GC allocation ???
std.internal.math.biguintcore includeSign 'new' causes GC allocation ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore mulInternal 'new' causes GC allocation ???
std.internal.math.biguintcore mulInternal 'delete' requires GC ???
std.internal.math.biguintcore mulInternal 'new' causes GC allocation ???
std.internal.math.biguintcore mulInternal 'delete' requires GC ???
std.internal.math.biguintcore BigDigit 'new' causes GC allocation ???
std.internal.math.biguintcore scratchbuff 'delete' requires GC ???
std.internal.math.biguintcore divModInternal 'new' causes GC allocation ???
std.internal.math.biguintcore divModInternal 'new' causes GC allocation ???
std.internal.math.biguintcore divModInternal 'delete' requires GC ???
std.internal.math.biguintcore divModInternal 'delete' requires GC ???
std.internal.math.biguintcore biguintToDecimal setting 'length' may cause GC allocation ???
std.internal.math.biguintcore the 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.opAssign array literal may cause GC allocation ???
std.internal.math.biguintcore blockDivMod 'new' causes GC allocation ???
std.internal.math.biguintcore blockDivMod 'delete' requires GC ???
std.internal.math.biguintcore BigUint.char 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.char 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.fromHexString 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.fromHexString array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.fromDecimalString array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.fromDecimalString 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.fromDecimalString setting 'length' may cause GC allocation ???
std.internal.math.biguintcore BigUint.opShl 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.mul array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.mul 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.divInt 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.modInt 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.modInt 'delete' requires GC ???
std.internal.math.biguintcore BigUint.div array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.div 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.mod array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.mod 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.mod 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.pow array literal may cause GC allocation ???
std.internal.math.biguintcore BigUint.pow 'new' causes GC allocation ???
std.internal.math.biguintcore BigUint.pow 'new' causes GC allocation ???
std.json JSONValue.assign indexing an associative array may cause GC allocation ???
std.json JSONValue.assign 'new' causes GC allocation ???
std.json JSONValue.inout operator ~ may cause GC allocation ???
std.json JSONValue.opIndexAssign indexing an associative array may cause GC allocation ???
std.json JSONValue.opBinary operator ~= may cause GC allocation ???
std.json JSONValue.opOpAssign operator ~= may cause GC allocation ???
std.json parseJSON 'new' causes GC allocation ???
std.json parseJSON indexing an associative array may cause GC allocation ???
std.json parseJSON operator ~= may cause GC allocation ???
std.json toJSON 'new' causes GC allocation ???
std.json toJSON indexing an associative array may cause GC allocation ???
std.mmfile MmFile.filename operator ~ may cause GC allocation ???
std.mmfile MmFile.filename operator ~ may cause GC allocation ???
std.mmfile MmFile.filename operator ~ may cause GC allocation ???
std.net.curl byLine array literal may cause GC allocation ???
std.net.curl byLine array literal may cause GC allocation ???
std.net.curl template using closure causes GC allocation CL3
std.net.curl template using closure causes GC allocation CL3
std.net.curl AsyncLineInputRange 'new' causes GC allocation ???
std.net.curl AsyncChunkInputRange 'new' causes GC allocation ???
std.net.curl decodeString(Char operator ~= may cause GC allocation ???
std.net.curl decodeLineInto setting 'length' may cause GC allocation ???
std.net.curl decodeLineInto operator ~= may cause GC allocation ???
std.net.curl decodeLineInto setting 'length' may cause GC allocation ???
std.net.curl decodeLineInto operator ~= may cause GC allocation ???
std.net.curl HTTP.Impl using closure causes GC allocation CL5
std.net.curl HTTP.Impl indexing an associative array may cause GC allocation ???
std.net.curl HTTP.url operator ~ may cause GC allocation ???
std.net.curl download using closure causes GC allocation CL1
std.net.curl download 'new' causes GC allocation ???
std.net.curl FTP.url operator ~ may cause GC allocation ???
std.net.curl SMTP.Impl using closure causes GC allocation CL5
std.net.curl upload using closure causes GC allocation CL1
std.net.curl upload 'new' causes GC allocation ???
std.net.curl Curl.onReceive using closure causes GC allocation CL5
std.net.curl Curl.onReceiveHeader using closure causes GC allocation CL5
std.net.curl Curl.onSend using closure causes GC allocation CL5
std.net.curl Curl.onSeek using closure causes GC allocation CL5
std.net.curl Curl.onSocketOption using closure causes GC allocation CL5
std.net.curl Curl.onProgress using closure causes GC allocation CL5
std.net.curl Pool.void 'new' causes GC allocation ???
std.net.curl _receiveAsyncChunks using closure causes GC allocation CL5
std.net.curl _finalizeAsyncChunks setting 'length' may cause GC allocation ???
std.net.curl _receiveAsyncLines using closure causes GC allocation CL3
std.net.curl _receiveAsyncLines setting 'length' may cause GC allocation ???
std.net.curl _receiveAsyncLines operator ~= may cause GC allocation ???
std.net.curl _spawnAsync using closure causes GC allocation CL3
std.net.curl _spawnAsync 'new' causes GC allocation ???
std.net.curl _spawnAsync setting 'length' may cause GC allocation ???
std.net.curl _spawnAsync 'new' causes GC allocation ???
std.net.curl del operator ~ may cause GC allocation ???
std.net.curl _basicHTTP using closure causes GC allocation CL1
std.net.curl _basicHTTP operator ~= may cause GC allocation ???
std.net.curl _basicHTTP operator ~= may cause GC allocation ???
std.net.curl _basicHTTP operator ~= may cause GC allocation ???
std.net.curl _basicHTTP indexing an associative array may cause GC allocation ???
std.net.curl _basicFTP using closure causes GC allocation CL1
std.net.curl _basicFTP operator ~= may cause GC allocation ???
std.net.isemail isEmail associative array literal may cause GC allocation ???
std.net.isemail isEmail associative array literal may cause GC allocation ???
std.net.isemail isEmail array literal may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail grep using closure causes GC allocation CL2
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail array literal may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail 'new' causes GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail 'new' causes GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail 'new' causes GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail 'new' causes GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~ may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail operator ~= may cause GC allocation ???
std.net.isemail isEmail indexing an associative array may cause GC allocation ???
std.net.isemail isEmail array literal may cause GC allocation ???
std.net.isemail isEmail array literal may cause GC allocation ???
std.numeric Fft.memSpace 'new' causes GC allocation ???
std.outbuffer OutBuffer.reserve setting 'length' may cause GC allocation ???
std.parallelism TaskPool.abstractPutNoSync 'new' causes GC allocation ???
std.parallelism TaskPool.abstractPutGroupNoSync 'new' causes GC allocation ???
std.parallelism TaskPool.task 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism TaskPool.nWorkers 'new' causes GC allocation ???
std.parallelism **** using closure causes GC allocation CL4
std.parallelism **** setting 'length' may cause GC allocation ???
std.parallelism **** setting 'length' may cause GC allocation ???
std.parallelism **** setting 'length' may cause GC allocation ???
std.parallelism **** setting 'length' may cause GC allocation ???
std.parallelism **** 'new' causes GC allocation ???
std.parallelism TaskPool.asyncBuf setting 'length' may cause GC allocation ???
std.parallelism TaskPool.asyncBuf setting 'length' may cause GC allocation ???
std.parallelism TaskPool.asyncBuf 'new' causes GC allocation ???
std.parallelism **** using closure causes GC allocation CL4
std.parallelism **** 'new' causes GC allocation ???
std.parallelism TaskPool.WorkerLocalStorage 'new' causes GC allocation ???
std.parallelism taskPool 'new' causes GC allocation ???
std.parallelism ) 'new' causes GC allocation ???
std.parallelism foreachErr 'new' causes GC allocation ???
std.parallelism RoundRobinBuffer.) setting 'length' may cause GC allocation ???
std.parallelism RoundRobinBuffer.) setting 'length' may cause GC allocation ???
std.parallelism Task.executeInNewThread 'new' causes GC allocation ???
std.parallelism Task.executeInNewThread 'new' causes GC allocation ???
std.parallelism task 'new' causes GC allocation ???
std.parallelism task 'new' causes GC allocation ???
std.parallelism task 'new' causes GC allocation ???
std.path **** setting 'length' may cause GC allocation ???
std.path buildNormalizedPath 'new' causes GC allocation ???
std.path buildNormalizedPath 'new' causes GC allocation ???
std.path absolutePath 'new' causes GC allocation ???
std.path relativePath 'new' causes GC allocation ???
std.path relativePath operator ~= may cause GC allocation ???
std.path relativePath operator ~= may cause GC allocation ???
std.path relativePath operator ~= may cause GC allocation ???
std.path relativePath operator ~= may cause GC allocation ???
std.path globMatch operator ~ may cause GC allocation ???
std.path expandTilde operator ~= may cause GC allocation ???
std.path expandTilde operator ~ may cause GC allocation ???
std.path expandTilde operator ~ may cause GC allocation ???
std.path setExtension operator ~ may cause GC allocation ???
std.path setExtension operator ~ may cause GC allocation ???
std.path setExtension operator ~= may cause GC allocation ???
std.path setExtension operator ~= may cause GC allocation ???
std.path setExtension operator ~= may cause GC allocation ???
std.path setExtension operator ~ may cause GC allocation ???
std.path defaultExtension operator ~ may cause GC allocation ???
std.path defaultExtension operator ~ may cause GC allocation ???
std.path **** 'new' causes GC allocation ???
std.process Pid.returns 'new' causes GC allocation ???
std.process pipe 'new' causes GC allocation ???
std.process pipe 'new' causes GC allocation ???
std.process pipe 'new' causes GC allocation ???
std.process pipeProcessImpl 'new' causes GC allocation ???
std.process pipeProcessImpl 'new' causes GC allocation ???
std.process ProcessPipes.stdin 'new' causes GC allocation ???
std.process ProcessPipes.stdout 'new' causes GC allocation ???
std.process ProcessPipes.stderr 'new' causes GC allocation ???
std.process ProcessException.newFromErrno operator ~ may cause GC allocation ???
std.process ProcessException.newFromErrno 'new' causes GC allocation ???
std.process TestScript.code operator ~ may cause GC allocation ???
std.process TestScript.code operator ~ may cause GC allocation ???
std.process uniqueTempPath operator ~ may cause GC allocation ???
std.process escapeWindowsShellCommand 'new' causes GC allocation ???
std.process escapeWindowsShellCommand 'new' causes GC allocation ???
std.process escapeShellArguments 'new' causes GC allocation ???
std.process escapeShellArguments setting 'length' may cause GC allocation ???
std.process charAllocator 'new' causes GC allocation ???
std.process environment.opIndex operator ~ may cause GC allocation ???
std.process environment.Exception operator ~ may cause GC allocation ???
std.process environment.toAA indexing an associative array may cause GC allocation ???
std.process use 'new' causes GC allocation ???
std.process use operator ~ may cause GC allocation ???
std.process execvpe_ operator ~ may cause GC allocation ???
std.process shell operator ~= may cause GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process spawnProcessImpl operator ~ may cause GC allocation ???
std.process spawnProcessImpl 'new' causes GC allocation ???
std.process createEnv 'new' causes GC allocation ???
std.process createEnv operator ~ may cause GC allocation ???
std.random uniformDistribution setting 'length' may cause GC allocation ???
std.random RandomCover.if setting 'length' may cause GC allocation ???
std.random RandomCover.if setting 'length' may cause GC allocation ???
std.random **** 'new' causes GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~= may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range roundRobin operator ~ may cause GC allocation ???
std.range Repeat.opSlice 'new' causes GC allocation ???
std.range Cycle.if 'new' causes GC allocation ???
std.range Cycle.opSlice 'new' causes GC allocation ???
std.range policy 'new' causes GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range lockstepMixin operator ~= may cause GC allocation ???
std.range put array literal may cause GC allocation ???
std.range putChar array literal may cause GC allocation ???
std.range OnlyResult.opIndex 'new' causes GC allocation ???
std.range OnlyResult.opSlice 'new' causes GC allocation ???
std.range OnlyResult.opIndex 'new' causes GC allocation ???
std.range OnlyResult.opSlice 'new' causes GC allocation ???
std.range OnlyResult.opIndex 'new' causes GC allocation ???
std.range OnlyResult.opSlice 'new' causes GC allocation ???
std.range enumerate 'new' causes GC allocation ???
std.range putMethods operator ~ may cause GC allocation ???
std.range putMethods operator ~= may cause GC allocation ???
std.range putMethods operator ~ may cause GC allocation ???
std.range InputRangeObject.if 'new' causes GC allocation ???
std.range inputRangeObject 'new' causes GC allocation ???
std.range outputRangeObject.E 'new' causes GC allocation ???
std.socket getAddressInfoImpl 'new' causes GC allocation ???
std.socket getAddressInfoImpl 'new' causes GC allocation ???
std.socket getAddressInfoImpl 'new' causes GC allocation ???
std.socket serviceToPort 'new' causes GC allocation ???
std.socket getAddress setting 'length' may cause GC allocation ???
std.socket getAddress 'new' causes GC allocation ???
std.socket getAddress 'new' causes GC allocation ???
std.socket getAddress operator ~= may cause GC allocation ???
std.socket getAddress 'new' causes GC allocation ???
std.socket parseAddress 'new' causes GC allocation ???
std.socket parseAddress 'new' causes GC allocation ???
std.socket Address.toHostString 'new' causes GC allocation ???
std.socket Address.toHostString 'new' causes GC allocation ???
std.socket Address.toHostString operator ~ may cause GC allocation ???
std.socket Address.toHostString 'new' causes GC allocation ???
std.socket Address.toHostString operator ~ may cause GC allocation ???
std.socket Address.toServiceString 'new' causes GC allocation ???
std.socket Address.toServiceString 'new' causes GC allocation ???
std.socket Address.toServiceString operator ~ may cause GC allocation ???
std.socket Address.toServiceString 'new' causes GC allocation ???
std.socket Address.toServiceString operator ~ may cause GC allocation ???
std.socket Address.string operator ~ may cause GC allocation ???
std.socket Address.string operator ~ may cause GC allocation ???
std.socket InternetAddress.char 'new' causes GC allocation ???
std.socket InternetAddress.char 'new' causes GC allocation ???
std.socket InternetAddress.string 'new' causes GC allocation ???
std.socket Internet6Address.parse 'new' causes GC allocation ???
std.socket if 'new' causes GC allocation ???
std.socket SocketSet.SocketSet setting 'length' may cause GC allocation ???
std.socket SocketSet.SocketSet setting 'length' may cause GC allocation ???
std.socket SocketSet.add setting 'length' may cause GC allocation ???
std.socket SocketSet.add setting 'length' may cause GC allocation ???
std.socket SocketOSException.msg operator ~ may cause GC allocation ???
std.socket Socket.af 'new' causes GC allocation ???
std.socket Socket.af 'new' causes GC allocation ???
std.socket Socket.blocking 'new' causes GC allocation ???
std.socket Socket.bind 'new' causes GC allocation ???
std.socket Socket.connect 'new' causes GC allocation ???
std.socket Socket.listen 'new' causes GC allocation ???
std.socket Socket.Socket 'new' causes GC allocation ???
std.socket Socket.accept 'new' causes GC allocation ???
std.socket Socket.hostName 'new' causes GC allocation ???
std.socket Socket.remoteAddress 'new' causes GC allocation ???
std.socket Socket.remoteAddress 'new' causes GC allocation ???
std.socket Socket.localAddress 'new' causes GC allocation ???
std.socket Socket.localAddress 'new' causes GC allocation ???
std.socket Socket.receiveFrom 'new' causes GC allocation ???
std.socket Socket.getOption 'new' causes GC allocation ???
std.socket Socket.getOption operator ~ may cause GC allocation ???
std.socket Socket.setOption 'new' causes GC allocation ???
std.socket Socket.setOption 'new' causes GC allocation ???
std.socket Socket.setOption operator ~ may cause GC allocation ???
std.socket Socket.setOption 'new' causes GC allocation ???
std.socket Socket.select 'new' causes GC allocation ???
std.socket Socket.Address 'new' causes GC allocation ???
std.socket Socket.Address 'new' causes GC allocation ???
std.socket Socket.Address 'new' causes GC allocation ???
std.socket socketPair 'new' causes GC allocation ???
std.socket socketPair 'new' causes GC allocation ???
std.socket Protocol.populate 'new' causes GC allocation ???
std.socket Service.populate 'new' causes GC allocation ???
std.socket InternetHost.validHostent 'new' causes GC allocation ???
std.socket InternetHost.populate 'new' causes GC allocation ???
std.socket InternetHost.populate 'new' causes GC allocation ???
std.socketstream SocketStream.SocketStream 'new' causes GC allocation ???
std.stdio ) operator ~ may cause GC allocation ???
std.stdio file operator ~ may cause GC allocation ???
std.stdio the operator ~ may cause GC allocation ???
std.stdio every setting 'length' may cause GC allocation ???
std.stdio every operator ~= may cause GC allocation ???
std.stdio every operator ~= may cause GC allocation ???
std.stdio every operator ~= may cause GC allocation ???
std.stdio file 'new' causes GC allocation ???
std.stdio file 'new' causes GC allocation ???
std.stdio file 'new' causes GC allocation ???
std.stdio LockingTextReader.front 'new' causes GC allocation ???
std.stdio LockingTextReader.popFront 'new' causes GC allocation ???
std.stdio lines.f operator ~= may cause GC allocation ???
std.stdio lines.f setting 'length' may cause GC allocation ???
std.stdio lines.f 'new' causes GC allocation ???
std.stdio ChunksImpl.f 'new' causes GC allocation ???
std.stdio ChunksImpl.f 'new' causes GC allocation ???
std.stdio ChunksImpl.f setting 'length' may cause GC allocation ???
std.stdio with operator ~ may cause GC allocation ???
std.stdio with 'new' causes GC allocation ???
std.stdio with 'new' causes GC allocation ???
std.stdio readlnImpl setting 'length' may cause GC allocation ???
std.stdio readlnImpl operator ~= may cause GC allocation ???
std.stdio readlnImpl setting 'length' may cause GC allocation ???
std.stdio readlnImpl setting 'length' may cause GC allocation ???
std.stdio readlnImpl 'new' causes GC allocation ???
std.stdio readlnImpl 'new' causes GC allocation ???
std.stdio readlnImpl 'new' causes GC allocation ???
std.stdio readlnImpl operator ~ may cause GC allocation ???
std.stdio _popen operator ~ may cause GC allocation ???
std.stdio to operator ~ may cause GC allocation ???
std.stdio to operator ~ may cause GC allocation ???
std.stdio the operator ~ may cause GC allocation ???
std.stdio file operator ~ may cause GC allocation ???
std.stdio file operator ~ may cause GC allocation ???
std.stdio for operator ~ may cause GC allocation ???
std.stream ungetcw operator ~= may cause GC allocation ???
std.stream ungetcw operator ~= may cause GC allocation ???
std.stream writeExact 'new' causes GC allocation ???
std.stream flush setting 'length' may cause GC allocation ???
std.stream string 'new' causes GC allocation ???
std.stream string 'new' causes GC allocation ???
std.stream string setting 'length' may cause GC allocation ???
std.stream void 'new' causes GC allocation ???
std.stream void 'new' causes GC allocation ???
std.stream void 'new' causes GC allocation ???
std.stream source 'new' causes GC allocation ???
std.stream TreadLine(T) operator ~= may cause GC allocation ???
std.stream void 'new' causes GC allocation ???
std.stream open operator ~ may cause GC allocation ???
std.stream open 'new' causes GC allocation ???
std.stream open operator ~ may cause GC allocation ???
std.stream ulong 'new' causes GC allocation ???
std.stream this() 'new' causes GC allocation ???
std.stream filename 'new' causes GC allocation ???
std.stream hFile 'new' causes GC allocation ???
std.stream wchar setting 'length' may cause GC allocation ???
std.stream wchar 'new' causes GC allocation ???
std.stream wchar 'new' causes GC allocation ???
std.stream data 'new' causes GC allocation ???
std.stream reserve setting 'length' may cause GC allocation ???
std.stream void 'delete' requires GC ???
std.stream readExact 'new' causes GC allocation ???
std.stream readLine setting 'length' may cause GC allocation ???
std.stream readLine operator ~= may cause GC allocation ???
std.stream readLine setting 'length' may cause GC allocation ???
std.stream readLineW setting 'length' may cause GC allocation ???
std.stream readLineW operator ~= may cause GC allocation ???
std.stream readLineW setting 'length' may cause GC allocation ???
std.stream readString 'new' causes GC allocation ???
std.stream readStringW 'new' causes GC allocation ???
std.stream getc setting 'length' may cause GC allocation ???
std.stream getcw setting 'length' may cause GC allocation ???
std.stream getcw 'new' causes GC allocation ???
std.stream ungetc setting 'length' may cause GC allocation ???
std.stream ungetc operator ~= may cause GC allocation ???
std.stream ungetcw setting 'length' may cause GC allocation ???
std.stream ungetcw operator ~= may cause GC allocation ???
std.string leftJustify 'new' causes GC allocation ???
std.string leftJustify 'new' causes GC allocation ???
std.string rightJustify 'new' causes GC allocation ???
std.string rightJustify 'new' causes GC allocation ???
std.string center 'new' causes GC allocation ???
std.string center 'new' causes GC allocation ???
std.string detab setting 'length' may cause GC allocation ???
std.string detab setting 'length' may cause GC allocation ???
std.string toStringz 'new' causes GC allocation ???
std.string detab setting 'length' may cause GC allocation ???
std.string entab setting 'length' may cause GC allocation ???
std.string entab setting 'length' may cause GC allocation ???
std.string entab setting 'length' may cause GC allocation ???
std.string entab setting 'length' may cause GC allocation ???
std.string translateImpl indexing an associative array may cause GC allocation ???
std.string translate 'new' causes GC allocation ???
std.string makeTrans 'new' causes GC allocation ???
std.string format 'new' causes GC allocation ???
std.string sformat using closure causes GC allocation CL6
std.string sformat 'new' causes GC allocation ???
std.string succ 'new' causes GC allocation ???
std.string soundex 'new' causes GC allocation ???
std.string abbrev indexing an associative array may cause GC allocation ???
std.string abbrev indexing an associative array may cause GC allocation ???
std.string wrap setting 'length' may cause GC allocation ???
std.string wrap setting 'length' may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string wrap operator ~= may cause GC allocation ???
std.string outdent 'new' causes GC allocation ???
std.syserror SysError.msg 'new' causes GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits **** operator ~= may cause GC allocation ???
std.traits std indexing an associative array may cause GC allocation ???
std.traits std associative array literal may cause GC allocation ???
std.traits isExpressionTuple.if associative array literal may cause GC allocation ???
std.traits fqnType.parametersTypeString array literal may cause GC allocation ???
std.traits fqnType.parametersTypeString array literal may cause GC allocation ???
std.traits fqnType.parametersTypeString operator ~= may cause GC allocation ???
std.typecons alignForSize operator ~ may cause GC allocation ???
std.typecons alignForSize operator ~= may cause GC allocation ???
std.typecons alignForSize operator ~ may cause GC allocation ???
std.typecons alignForSize operator ~= may cause GC allocation ???
std.typecons alignForSize operator ~ may cause GC allocation ???
std.typecons alignForSize operator ~= may cause GC allocation ???
std.typecons alignForSize operator ~ may cause GC allocation ???
std.typecons alignForSize operator ~= may cause GC allocation ???
std.typecons if 'delete' requires GC ???
std.typecons NotImplementedError.method operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~ may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons **** operator ~= may cause GC allocation ???
std.typecons **** array literal may cause GC allocation ???
std.typecons wrap.wrap(Source) 'new' causes GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons wrap.wrap(Source) operator ~= may cause GC allocation ???
std.typecons Tuple.injectNamedFields operator ~= may cause GC allocation ???
std.typecons Tuple.injectNamedFields operator ~= may cause GC allocation ???
std.uni genUnrolledSwitchSearch operator ~= may cause GC allocation ???
std.uni genUnrolledSwitchSearch operator ~= may cause GC allocation ???
std.uni genUnrolledSwitchSearch operator ~= may cause GC allocation ???
std.uni GcPolicy.alloc 'new' causes GC allocation ???
std.uni GcPolicy.realloc setting 'length' may cause GC allocation ???
std.uni GcPolicy.append operator ~= may cause GC allocation ???
std.uni InversionList.set operator ~= may cause GC allocation ???
std.uni InversionList.set operator ~= may cause GC allocation ???
std.uni InversionList.inverted array literal may cause GC allocation ???
std.uni InversionList.inverted array literal may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~ may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~ may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~ may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~ may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~ may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.toSourceCode operator ~= may cause GC allocation ???
std.uni InversionList.dropUpTo array literal may cause GC allocation ???
std.uni InversionList.skipUpTo array literal may cause GC allocation ???
std.uni Utf8Matcher.badEncoding 'new' causes GC allocation ???
std.uni Utf8Matcher.template operator ~= may cause GC allocation ???
std.uni Utf8Matcher.template operator ~= may cause GC allocation ???
std.uni Utf8Matcher.template operator ~= may cause GC allocation ???
std.uni Utf16Matcher.badEncoding 'new' causes GC allocation ???
std.uni toDelegate using closure causes GC allocation CL5
std.uni compressTo operator ~= may cause GC allocation ???
std.uni compressTo operator ~= may cause GC allocation ???
std.uni compressTo operator ~= may cause GC allocation ???
std.uni compressTo operator ~= may cause GC allocation ???
std.uni compressTo operator ~= may cause GC allocation ???
std.uni compressTo operator ~= may cause GC allocation ???
std.uni isPrettyPropertyName array literal may cause GC allocation ???
std.uni SetSearcher.opCall 'new' causes GC allocation ???
std.uni SetSearcher.opCall operator ~ may cause GC allocation ???
std.uni unicode.loadAny 'new' causes GC allocation ???
std.uni unicode.loadAny operator ~ may cause GC allocation ???
std.uni enum operator ~= may cause GC allocation ???
std.uni enum operator ~= may cause GC allocation ???
std.uni enum setting 'length' may cause GC allocation ???
std.uni enum setting 'length' may cause GC allocation ???
std.uni enum setting 'length' may cause GC allocation ???
std.uni encodeTo 'new' causes GC allocation ???
std.uni toCaseInPlaceAlloc.toCaseInPlaceAlloc 'new' causes GC allocation ???
std.uni MultiArray.sizes 'new' causes GC allocation ???
std.uni MultiArray.n setting 'length' may cause GC allocation ???
std.uni MultiArray.n setting 'length' may cause GC allocation ???
std.uri URI_Encode 'new' causes GC allocation ???
std.uri URI_Encode 'new' causes GC allocation ???
std.uri URI_Encode 'new' causes GC allocation ???
std.uri URI_Encode 'new' causes GC allocation ???
std.uri URI_Encode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URI_Decode 'new' causes GC allocation ???
std.uri URIException.nothrow operator ~ may cause GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf decodeImpl 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode operator ~= may cause GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode operator ~= may cause GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode operator ~= may cause GC allocation ???
std.utf encode operator ~= may cause GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode 'new' causes GC allocation ???
std.utf encode operator ~= may cause GC allocation ???
std.utf strideImpl 'new' causes GC allocation ???
std.utf toUTF8 setting 'length' may cause GC allocation ???
std.utf toUTF8 setting 'length' may cause GC allocation ???
std.utf toUTF8 setting 'length' may cause GC allocation ???
std.utf toUTF8 setting 'length' may cause GC allocation ???
std.utf toUTF16 setting 'length' may cause GC allocation ???
std.utf toUTF16 setting 'length' may cause GC allocation ???
std.utf toUTF16 operator ~= may cause GC allocation ???
std.utf wstring setting 'length' may cause GC allocation ???
std.utf wstring setting 'length' may cause GC allocation ???
std.utf toUTF32 setting 'length' may cause GC allocation ???
std.utf toUTF32 setting 'length' may cause GC allocation ???
std.utf toUTFzImpl array literal may cause GC allocation ???
std.utf toUTFzImpl operator ~= may cause GC allocation ???
std.utf nothrow 'new' causes GC allocation ???
std.utf nothrow 'new' causes GC allocation ???
std.utf nothrow 'new' causes GC allocation ???
std.utf strideBack 'new' causes GC allocation ???
std.utf strideBack 'new' causes GC allocation ???
std.utf UTFException.msg operator ~ may cause GC allocation ???
std.utf UTFException.string operator ~= may cause GC allocation ???
std.utf toUCSindex 'new' causes GC allocation ???
std.utf toUCSindex 'new' causes GC allocation ???
std.utf UTFException.string operator ~= may cause GC allocation ???
std.utf UTFException.string operator ~= may cause GC allocation ???
std.uuid parseUUID 'new' causes GC allocation throws Exception
std.uuid parseUUID 'new' causes GC allocation throws Exception
std.uuid parseUUID 'new' causes GC allocation throws Exception
std.uuid **** 'new' causes GC allocation throws Exception
std.uuid **** 'new' causes GC allocation throws Exception
std.uuid **** 'new' causes GC allocation throws Exception
std.uuid **** 'new' causes GC allocation throws Exception
std.uuid **** 'new' causes GC allocation throws Exception
std.variant variantArray operator ~= may cause GC allocation ???
std.variant VariantException operator ~ may cause GC allocation ???
std.variant visitImpl 'new' causes GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler indexing an associative array may cause GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler indexing an associative array may cause GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler array literal may cause GC allocation ???
std.variant VariantN.handler operator ~= may cause GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.handler 'new' causes GC allocation ???
std.variant VariantN.opAssign 'new' causes GC allocation ???
std.variant VariantN.get 'new' causes GC allocation ???
std.variant VariantN.get 'new' causes GC allocation ???
std.variant VariantN.value 'new' causes GC allocation ???
std.variant VariantN.opArithmetic 'new' causes GC allocation ???
std.xml Tag.tagString operator ~ may cause GC allocation ???
std.xml Tag.tagString operator ~ may cause GC allocation ???
std.xml Tag.string operator ~ may cause GC allocation ???
std.xml Tag.string operator ~ may cause GC allocation ???
std.xml Tag.string indexing an associative array may cause GC allocation ???
std.xml Tag.string 'new' causes GC allocation ???
std.xml Tag.string setting 'length' may cause GC allocation ???
std.xml Tag.string setting 'length' may cause GC allocation ???
std.xml Tag.string 'new' causes GC allocation ???
std.xml Tag.const operator ~ may cause GC allocation ???
std.xml Tag.const operator ~= may cause GC allocation ???
std.xml Tag.const operator ~ may cause GC allocation ???
std.xml Tag.const operator ~ may cause GC allocation ???
std.xml Tag.const operator ~ may cause GC allocation ???
std.xml Comment.content 'new' causes GC allocation ???
std.xml Comment.string operator ~ may cause GC allocation ???
std.xml CData.content 'new' causes GC allocation ???
std.xml CData.string operator ~ may cause GC allocation ???
std.xml XMLInstruction.content 'new' causes GC allocation ???
std.xml XMLInstruction.string operator ~ may cause GC allocation ???
std.xml ProcessingInstruction.content 'new' causes GC allocation ???
std.xml ProcessingInstruction.string operator ~ may cause GC allocation ???
std.xml Item.pretty array literal may cause GC allocation ???
std.xml DocumentParser.xmlText_ operator ~ may cause GC allocation ???
std.xml ElementParser.parse indexing an associative array may cause GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse indexing an associative array may cause GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse indexing an associative array may cause GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse indexing an associative array may cause GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.parse 'new' causes GC allocation ???
std.xml ElementParser.msg 'new' causes GC allocation ???
std.xml ElementParser.msg 'new' causes GC allocation ???
std.xml ElementParser.msg 'new' causes GC allocation ???
std.xml ElementParser.checkAttValue operator ~ may cause GC allocation ???
std.xml ElementParser.checkElement operator ~ may cause GC allocation ???
std.xml ElementParser.checkLiteral operator ~ may cause GC allocation ???
std.xml ElementParser.checkEnd 'new' causes GC allocation ???
std.xml ElementParser.checkEnd operator ~ may cause GC allocation ???
std.xml check 'new' causes GC allocation ???
std.xml CheckException.string operator ~= may cause GC allocation ???
std.xml CheckException.string operator ~= may cause GC allocation ???
std.xml CheckException.string operator ~ may cause GC allocation ???
std.xml Err 'new' causes GC allocation ???
std.xml Err 'new' causes GC allocation ???
std.xml Err operator ~= may cause GC allocation ???
std.xml Err operator ~= may cause GC allocation ???
std.xml Err 'new' causes GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode 'new' causes GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml decode 'new' causes GC allocation ???
std.xml decode operator ~= may cause GC allocation ???
std.xml Document.s 'new' causes GC allocation ???
std.xml Document.const operator ~ may cause GC allocation ???
std.xml Element.name 'new' causes GC allocation ???
std.xml Element.name 'new' causes GC allocation ???
std.xml Element.tag_ 'new' causes GC allocation ???
std.xml Element.tag_ indexing an associative array may cause GC allocation ???
std.xml Element.opCatAssign operator ~= may cause GC allocation ???
std.xml Element.opCatAssign operator ~= may cause GC allocation ???
std.xml Element.opCatAssign operator ~= may cause GC allocation ???
std.xml Element.opCatAssign operator ~= may cause GC allocation ???
std.xml Element.opCatAssign operator ~= may cause GC allocation ???
std.xml Element.appendItem operator ~= may cause GC allocation ???
std.xml Element.parse using closure causes GC allocation CL6
std.xml Element.parse 'new' causes GC allocation ???
std.xml Element.parse 'new' causes GC allocation ???
std.xml Element.parse 'new' causes GC allocation ???
std.xml Element.parse 'new' causes GC allocation ???
std.xml Element.parse indexing an associative array may cause GC allocation ???
std.xml Element.parse 'new' causes GC allocation ???
std.xml Element.const 'new' causes GC allocation ???
std.xml Element.const operator ~= may cause GC allocation ???
std.xml Element.const array literal may cause GC allocation ???
std.xml Element.const array literal may cause GC allocation ???
std.xml Element.const operator ~ may cause GC allocation ???
std.xml Element.const array literal may cause GC allocation ???
std.xml Element.const operator ~= may cause GC allocation ???
std.xml Element.const operator ~= may cause GC allocation ???
std.xml Element.const operator ~= may cause GC allocation ???
std.xml Element.const operator ~= may cause GC allocation ???
std.zip ArchiveMember.expandedData setting 'length' may cause GC allocation ???
std.zip ArchiveMember.compressionMethod 'new' causes GC allocation ???
std.zip ZipArchive.addMember indexing an associative array may cause GC allocation ???
std.zip ZipArchive.build 'new' causes GC allocation ???
std.zip ZipArchive.build 'new' causes GC allocation ???
std.zip ZipArchive.build 'new' causes GC allocation ???
std.zip ZipException.msg operator ~ may cause GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.buffer indexing an associative array may cause GC allocation ???
std.zip ZipArchive.buffer 'new' causes GC allocation ???
std.zip ZipArchive.expand 'new' causes GC allocation ???
std.zip ZipArchive.expand 'new' causes GC allocation ???
std.zip ZipArchive.expand 'new' causes GC allocation ???
std.zip ZipArchive.expand 'new' causes GC allocation ???
std.zlib compress 'new' causes GC allocation ???
std.zlib compress 'delete' requires GC ???
std.zlib compress 'new' causes GC allocation ???
std.zlib compress setting 'length' may cause GC allocation ???
std.zlib uncompress 'new' causes GC allocation ???
std.zlib uncompress setting 'length' may cause GC allocation ???
std.zlib uncompress setting 'length' may cause GC allocation ???
std.zlib uncompress 'new' causes GC allocation ???
std.zlib uncompress 'new' causes GC allocation ???
std.zlib Compress.error 'new' causes GC allocation ???
std.zlib Compress.compress 'new' causes GC allocation ???
std.zlib Compress.compress operator ~ may cause GC allocation ???
std.zlib Compress.compress 'delete' requires GC ???
std.zlib Compress.compress setting 'length' may cause GC allocation ???
std.zlib Compress.flush operator ~= may cause GC allocation ???
std.zlib Compress.flush 'delete' requires GC ???
std.zlib Compress.flush operator ~= may cause GC allocation ???
std.zlib UnCompress.error 'new' causes GC allocation ???
std.zlib UnCompress.uncompress 'new' causes GC allocation ???
std.zlib UnCompress.uncompress operator ~ may cause GC allocation ???
std.zlib UnCompress.uncompress 'delete' requires GC ???
std.zlib UnCompress.uncompress setting 'length' may cause GC allocation ???
std.zlib UnCompress.flush 'new' causes GC allocation ???
std.zlib UnCompress.flush operator ~= may cause GC allocation ???
std.zlib UnCompress.flush 'delete' requires GC ???
std.zlib UnCompress.flush operator ~ may cause GC allocation ???

Closure allocation reasons

CL01: Fixable by manually stack-allocating closure

  A delegate is passed to some function which stores this delegate and
  therefore correctly doesn't mark the parameter as scope. However,
  the lifetime of the stored delegate is still limited to the current
  function (e.g. it's stored in a struct instance, but on the stack).

  Can be fixed by creating a static struct{T... members; void
  doSomething(){access members}} instance on stack and passing
  &stackvar.doSomething as delegate.

CL02: Using delegates to add state to ranges

  ----
  return iota(dim).
    filter!(i => ptr[i])().
    map!(i => BitsSet!size_t(ptr[i], i * bitsPerSizeT))().
    joiner();
  ----
  This code adds state to ranges without declaring a new type: the ptr
  variable is not accessible and needs to be move into a closure.
  Declaring a custom range type is a solution, but not
  straightforward: If the ptr field is moved into the range a closure
  is not necessary. But if the range is copied, it's address changes
  and the delegate passed to map is now invalid.

CL03: Functions taking delegates as generic parameters

  receiveTimeout,receive,formattedWrite accept different types,
  including delegates. The delegates can all be scope to avoid the
  allocation but is void foo(T)(scope T) a good idea? The alternative
  is probably making an overload for delegates with scope attribute.

  (The result is that all functions calling receiveTimeout,... with a
  delegate allocate a closure)

CL04: Solvable with manual memory management

  Some specific functions can't be easily fixed, but the delegates
  they create have a well defined lifetime (for example spawn creates
  a delegate which is only needed at the startup of a new thread, it's
  never used again). These could be malloc+freed.

CL05: Design issue

  These functions generally create a delegate using variables passed
  in as parameters. There's no way to avoid closures here. Although
  manual allocation is an possible, the lifetime is undefined and can
  only be managed by the GC.

CL06: Other

  Two cases can be fixed by moving a buffer into a struct or moving a
  function out of a member function into it's surrounding class.
Retrieved from "https://wiki.dlang.org/?title=Stuff_in_Phobos_That_Generates_Garbage&oldid=4838"