Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Brian Greeson4,034 Points
Why are the call to super and the initialization of properties not in the opposite order as in many other languages
Why are the call to super and the initialization of properties not in the opposite order as in many other languages such as java
Java might be super(someArg); setSubclassfield()
this ensure the subclass is completely set-up prior to initializing the class which extends it. I assume the same order of execution would be required in swift.
Why, then, does swift demand that subclass properties are set before the call to super.init? Is the execution actually performed as written in swift?