If you enable -wstrict-selector-matching in your unit tests you'll get
many errors with OCMock mock objects since they will be of type id and
any selector that is referenced must be unique across all types in order
to avoid this error.
Given this is a pretty fundamental aspect of how mocks and OCMock work,
I believe silencing errors here is the right strategy vs disabling this
warning entirely for unit test code.
rahul-malik
commented
5 years ago
If you enable
-wstrict-selector-matchingin your unit tests you'll get many errors with OCMock mock objects since they will be of typeidand any selector that is referenced must be unique across all types in order to avoid this error.Given this is a pretty fundamental aspect of how mocks and OCMock work, I believe silencing errors here is the right strategy vs disabling this warning entirely for unit test code.