New lesson learned: In Java, object creation only happens at runtime.

A a = new B();
a.doSomething();

Compiler steps:
- checks if A exists
- checks if B exists
- checks if B is subclass of A
- compiles (code -> Bytecode)

Runtime:
- checks if B overrides doSomething() of A
- executes the overridden version

That's kinda how OO langs work though

Java doesn't really check that whether the func was overriden or not, it just fetches the function pointer for func doSomething from the vtable and calls that

More sophisticated compilers will do some shenanigans like devirtulization where they can see if only one concrete subclass exists, they will just statically call the method without lookup first

@12bitfloat vtable triggered some repressed memories from my c++ time.
Now I need vodka to make them disappear again…

@Lensflare do you drink? I am so disappointed :(

@whimsical I don’t. But I need to maintain the facade because everyone is expecting me to do it because I‘m a dev.

@Lensflare 'Now I need vodka (...)'.

This reminds me... https://youtube.com/watch/... .

@Lensflare that`s also the reason you wear sandals right? RIGHT?

@Lensflare that`s also the reason you wear sandals right? RIGHT?

@whimsical no, I wear sandals for style, not because I‘m a dev.

@whimsical actually that’s a lie. I wear sandals because I don’t give a shit about style 🤣