Skip to content

Fix super constructor not being called / required to be called #375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dcodeIO opened this issue Dec 13, 2018 · 2 comments
Closed

Fix super constructor not being called / required to be called #375

dcodeIO opened this issue Dec 13, 2018 · 2 comments

Comments

@dcodeIO
Copy link
Member

dcodeIO commented Dec 13, 2018

This is a tracking issue for super(...) calls in constructors, which doesn't work currently for no good reason.

@dcodeIO
Copy link
Member Author

dcodeIO commented Dec 13, 2018

Also: Document limitations of virtual (here: overloaded) members due to virtual lookup tables not being implemented yet (here: missing runtime type information), i.e.

class A {
  foo(): i32 { return 0; }
}
class B extends A {
  foo(): i32 { return 1; }
}

(new B() as A).foo() == 0

@MaxGraey
Copy link
Member

MaxGraey commented Feb 7, 2019

@dcodeIO Is this issue still present?

@dcodeIO dcodeIO closed this as completed Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants