I think your wrong about what remove does, `axes=axes.remove(axis.length.uniform)`

...import std.random;
import std.algorithm.mutation : remove;

enum Axis { None, X, Y, Z }

void...

...have the flexibility to improve it or remove it in a future edition without worrying...

...probably more of a rename than a remove.

I didn't think about using writeln...

...I rely on the optimiser now
to remove them? It looks like yet-another-workaround...

...all agreed that we couldn't just remove members from legacy objects. He thought managing...

...treat that as @system (and preferably also remove the implicit slicing of static arrays), then...

Well, you'd have been wrong. Just remove @safe at that point.

...sense, and the result is we cannot remove alias this, but we cannot fix it...

Do hate value types for not being consistent with reference types then? That’s the main...