pod spec lint not validating -Wno-* compiler flags

[mxcl]

Referring to this Twitter conversation and this screenshot:

In this case not preventing the warning would result in ~400 warnings for the end user. My choices were using the warning or putting every method in YOLOKit into a separate category, which was doable, but would make adding new methods in the future tedious, and something I wanted to avoid. The warning in this case was irrelevant for the library itself, and I only wanted the warning to apply when compiling YOLOKit itself, not outside of it.

In the end I worked around it with a clang pragma which I then include from every .m.

IMO as long as the warning flags don't propagate to the main project, CocoaPods could make this acceptable but maybe continue to refuse -w.

The specific flag here is -Wno-incomplete-implementation and I applied it as I have a single category (YOLO) for the library, but I split all the implementations across many files in order to make every method its own module. Clang would then warn in every file that the implementations were not complete, but they were, just not in the compilation unit.

[fabiopelosin]

Some context:

• We are trusting Xcode default configuration for the warnings as a sensible choice.
• We decided to keep the warnings visible for the betterment of the ecosystem and to encourage the submissions of patches aimed at addressing them. The same logic applies is the reason why we are printing a warning if they are disabled.
• Clang pragmas are a great way to deal with edge cases.

[fabiopelosin]

@CocoaPods/core ping

[fabiopelosin]

The consensus appears to be that pragma directives should be used in cases like this.

[NSExceptional]

That's an interesting conclusion to come to. Shouldn't it be up to the author, whose warnings flags will end up being used to compile their source anyway?