Avoiding GC in D and code consistancy

[Tim Hsu]

On Sunday, 31 December 2017 at 07:32:50 UTC, Ali Çehreli wrote:
> On 12/30/2017 11:16 PM, Tim Hsu wrote:
>
> > Struct version of Vector3f can't derive toString
> > method. writeln() prints unformated struct members. I know I
> can use
> > helper function here. But is there any other way?
>
> The normal way that I know is to insert a function like the 
> following into Vector3f:
>
>     string toString() {
>         import std.string : format;
>         return format("%s,%s,%s", x, y, z);
>     }
>
> > class version of Vector3f. Require new operator in
> opBinary(). scoped!
> > won't work here.
> >
> > Is there a better to write vector3f class while avoiding GC?
>
> Yeah, it doesn't make sense that a type of x, y, z should be a 
> class. I would stay with a struct here.
>
> Ali

Sorry I am a bit disappointed. It seems writeln itself will check 
if the struct to be printed has toString. If not, it use default 
struct printer.