allow for custom protocol implementations to skip Has* methods #282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please consider this change carefully - I'm not so familiar with the implications.
In experimenting with implementing a protocol using a custom struct, I found that for optional methods, the
HasXXX
method was required. This change makes it such that if the methodXXX
is implemented, but the correspondingHasXXX
is not implemented, the method/selector is considered to be implemented.This came out of me exploring the tableview example. Here's a significantly simpler version of the example (albeit without the dynamically changing data) using a custom
NSTableViewDataSource
implementation:https://gist.github.com/daaku/be2cd99b492cfc75ba1efe23ca56acd0