Skip to content
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

Make all designated initializers in AcknowListViewController public #66

Merged
merged 2 commits into from
Apr 10, 2020

Conversation

klmitchell2
Copy link

init(nibName nibNameOrNil: String?, bundle nibBundleOrNil: Bundle?) initializer needs to be public in order for a subclass of AcknowListViewController to use the convenience initializer.

Xcode release notes:

Convenience initializer inheritance for subclasses defined outside the module that defines the base class now comes with additional restrictions. When these subclasses have a base class with non-public designated initializers, they no longer automatically inherit convenience initializers from their superclasses. To restore this automatic inheritance behavior, the base class must ensure that all of its designated initializers are public or open. (51249311)

https://developer.apple.com/documentation/xcode_release_notes/xcode_11_4_release_notes

@klmitchell2 klmitchell2 changed the title Make all designated initializers public Make all designated initializers in AcknowListViewController public Apr 9, 2020
@vtourraine
Copy link
Owner

Thank you for the pull request! You’re totally right, this needs to be fixed.

But now that I’m looking at it, I just don’t see the need to override this particular initializer, since it only forwards to the super implementation. Am I missing something, or can we just remove this function?

@vtourraine vtourraine added the bug label Apr 10, 2020
@klmitchell2
Copy link
Author

You could also remove the function. I can update this PR with that change if you'd like.

@vtourraine
Copy link
Owner

Yes, please, that’d be great 🙌

@vtourraine vtourraine merged commit 1925a79 into vtourraine:master Apr 10, 2020
@vtourraine
Copy link
Owner

Great, thank you! Less code, less problems (I guess).

I’ll wait for a couple of days to make sure no one has any problem with it, then I’ll tag it as a new pod version.

@klmitchell2
Copy link
Author

Awesome thanks for the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants