Re: [boost] [Boost-users] [signals2][variant] inline warning with MSVC 2022

Am 22.09.22 um 06:24 schrieb Frank Mori Hess via Boost:

...

That's not very user friendly; maybe the user _wants_ the warning in his code, and the above would disable it even if no Boost header that uses BOOST_FORCEINLINE (and generates a warning) has been included. Okay, then maybe BOOST_FORCEINLINE shouldn't be defined as __force_inline on compilers where it doesn't actually force inlining. If the compiler is just going to treat it as a suggestion, I don't see

On Wed, Sep 21, 2022 at 12:32 PM Peter Dimov wrote: the point of boost headers using it and then suppressing the warning.

I'd rather see the headers generating this warning also suppress them. Yes it may not actually "force" inlining but IIRC it serves as a strong hint to the compiler, so removing it is not a good choice.