On Friday, 8 September 2023 at 19:48:33 UTC, Basile B. wrote:
My idea was that if you dont have defined a copy constructor
and if an instance is assigned to another, then that other
instance share the same pointer, which can cause memory errors.
To eliminate that risk and to detect where default
post-blitting may happen you can add
```d
@disable this(this);
```
to the struct.
Thank you! I did and I got a bunch of errors! Seeing where they
are located, it doesn't seem to be in the file and instances that
give me the error. Something really weird happens.
I'll probably return to my own memory allocated and fix the bugs
I had there, it will probably take me less time...
