Closed sg-s closed 3 years ago
No, only connect() isn't doing its job, possibly because there are 3 different connect functions, and name mangling doesn't work the way I expect it to
But maybe a compile time error is preferable? The error message is more obscure, but it happens earlier...
The "correct" way to fix this would be to change all the connect methods to have differnet names...
OK, renaming the connect methods fixes this -- confirming that it was a name mangling issue. Now we need to overhaul all mechanisms to support the new method names.
For example, the virtual connect methods in mechanism are never called, even when they should be. Instead of getting a runtime error with useful information, we get a compile-time error.