How about the hundreds of other possible warnings Lint can produce?
Are you going to write inline code for those too?
If you use a tool and that tool has some unwanted side effects and the tool has an option built in to circumvent that side effect, i say use it or use a different tool.
If you are using an actual Lint, that one has a configuration file to suppress warnings. And for any normal codebase with reasonably set up tooling suppressing warnings is an exception, not a rule.
And yes, if a certain warning has to stay on, I am totally happy to write a (commented) cryptic oneliner to avoid a spurious warning than to spew something like this all over the codebase whenever there is one:
#ifdef _MSC_VER
#pragma warnings (push)
#pragma warning(disable:XXXX)
#endif
#ifdef __GNUC__
// do something to disable the warning in GCC
#endif
#ifdef __clang__
// do something for Clang
#endif
the offending line of code here;#ifdef _MSC_VER
#pragma warning (pop)
#endif
#ifdef __GNUC__
// restore the GCC warning
#endif
#ifdef __clang__
// restore the Clang warning
#endif
....
And this handles only Visual C++, GCC and Clang - all very common if you are building for Windows (MSVC + GCC), Mac (Clang) and Linux (GCC+Clang). Wonderfully readable code, isn't it?
Once you have to deal with this, you will start to appreciate those one-liners, especially for stupid stuff like unused function arguments or local variables.