[REIMPLEMENTATION] Discuss how to handle constructor, destructor, assign, etc.

[TheRedDaemon]

Some classes have constructors, for example src\OpenSHC\Random\RNG.hpp

RNG(RNG const&);
void operator=(RNG const&);

RNG();
~RNG();

In cases where we can not assume the default was used, like in this example (RNG* Constructor_RNG()), we need to provide an implementation for them, calling the MACRO function.

How do we handle this?
Another cpp file with these, like RNG.cpp, next to the function files?

[gynt]

Classes were perhaps initialized with: Class clss = { 1, 2, 3}. Such initializers were probably converted into constructor functions by the compiler/linker (the ones we found to be called by __cinit. Rather than explicitly calling those functions (which is fine for the time being if need them), we eventually want to just initialize them correctly using MACRO_STRUCT_INSTANCE(addr) {1, 2, 3}. There are only a handful of classes with true constructors as the other ones are just singletons.

True classes have a real constructor e.g., MenuModal. We can place these in their own file e.g. MenuModal.cpp or place them in the headers at some point. Having the constructors be real constructors and not just proxies to call a constructor-this-function (which basically what the binary does anyway btw), is something that can only be done when the resolver system is removed.

So in terms of binary accuracy we are fine with using a proxy system.