Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@elextr it mostly does, but that's not my point. My point is that if you have an "interface" implemented by several classes:
class Iface {
public:
virtual bool maybeDoSomething(int n) = 0;
};
class Foo : public Iface {
public:
virtual bool maybeDoSomething(int n) override { return n == 42; }
};
class Bar : public Iface {
public:
virtual bool maybeDoSomething(int n) override { return (n % 42) == 0; }
};
Having the signature is fairly irrelevant: it's gonna always be the same. What's interesting is the symbol name and scope, and as that'll usually be spread in different files, the source file isn't useless.
Having the signature is useful when having overloads, not really for overrides.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.