fix: Use idup for string handling in non-GC memory allocation tests

gedaiu · gedaiu · commit c74139dea67a · 2025-12-12T22:09:39.000+01:00
diff --git a/source/fluentasserts/operations/memory/nonGcMemory.d b/source/fluentasserts/operations/memory/nonGcMemory.d
@@ -92,8 +92,8 @@ version (linux) {
     (() @trusted => free(leaked))();
 
     expect(evaluation.result.expected[]).to.equal(`not to allocate non-GC memory`);
-    expect(evaluation.result.actual[]).to.startWith("allocated ");
-    expect(evaluation.result.actual[]).to.contain("MB");
+    expect(evaluation.result.actual[].idup).to.startWith("allocated ");
+    expect(evaluation.result.actual[].idup).to.contain("MB");
   }
 }
 

Original file line number	Diff line number	Diff line change
`@@ -92,8 +92,8 @@ version (linux) {`
`92`	`92`	`(() @trusted => free(leaked))();`
`93`	`93`
`94`	`94`	expect(evaluation.result.expected[]).to.equal(`not to allocate non-GC memory`);
`95`		`- expect(evaluation.result.actual[]).to.startWith("allocated ");`
`96`		`- expect(evaluation.result.actual[]).to.contain("MB");`
	`95`	`+ expect(evaluation.result.actual[].idup).to.startWith("allocated ");`
	`96`	`+ expect(evaluation.result.actual[].idup).to.contain("MB");`
`97`	`97`	`}`
`98`	`98`	`}`
`99`	`99`