Opaque types conflict when present in multiple modules

[sethrj]

If module A has a function that interacts with a SWIGTYPE (generic match for int* and classes), it will generate a derived type SWIGTYPE_p_int. If module B imports module A and also has a function that uses that same type, it too will generate the opaque type. Unfortunately, that means that the new type is incompatible with the old (meaning you will be unable to pass the same type between C++ functions), and even worse it generates a build error because module B has a use a statement that imports the type, so the names will confict.

Identified by @balos1