You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some projects using pretty strict warning levels on their builds; raising the warning levels on the protobuf builds themselves should help ensure the code (and generated code) passes tighter checks.
The text was updated successfully, but these errors were encountered:
Working on protocolbuffers#1599, specifically:
- Turn on more warnings that the Xcode UI calls out with individual controls.
- Manually add:
-Wundef
-Wswitch-enum
- Manually add and then diable in the unittests because of XCTest's headers:
-Wreserved-id-macro
-Wdocumentation-unknown-command
- Manually add -Wdirect-ivar-access, but disable it for the unittests and in
the library code (via #pragmas to suppress it). This is done so proto users
can enable the warning.
#1617 is adding one more warning, and with that I think I'm calling this closed. We can look at adding other specific warnings as folks hit issues, but these seems to get most of what Xcode exposes and what I've seen a some other projects turning on.
Some projects using pretty strict warning levels on their builds; raising the warning levels on the protobuf builds themselves should help ensure the code (and generated code) passes tighter checks.
The text was updated successfully, but these errors were encountered: