09:35
Hey @MathieuGuindon are the Guard clauses you use located anywhere I can copy? Also I'm wondering if IFoo interface + DefaultFoo / CustomFoo1 implementing it is idiomatic VBA - if I can implement any class then why not just have CustomFoo1 implement DefaultFoo?
Basically IFoo in c# makes sense because interfaces and classes are different things and inheritance is possible so we implement interfaces and inherit classes and it's helpful for the mental model to keep that distinction. But for VBA it feels like a bit shoe-horned since there is no inheritance we can use classes for implementing.
Not sure if they makes sense, I'm just keen to sanity check any convention that the language does not enforce/endorse, like "never instantiate an interface" even though that is totally allowed in VBA. Why do we need the extra dummy interface class?