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

From: Frank Mori Hess (fmh6jj_at_[hidden])
Date: 2022-09-22 20:24:06

On Thu, Sep 22, 2022 at 8:57 AM Peter Dimov <pdimov_at_[hidden]> wrote:
>
> That's complete nonsense. First, Microsoft invented __forceinline, so
> making BOOST_FORCEINLINE be a no-op on the very compiler for which
> the feature has been added would be ridiculous. Second, it does force
> inlining, that's why it's called __forceinline. The whole point of the warning
> is to warn about the rare cases where the compiler does not honor the
> command; it exists because people want to know whether their "force
> inline" orders are ignored.

But no boost user wants to be warned about some internal
implementation detail of a boost library.  So every boost usage of
BOOST_FORCEINLINE needs to add a #pragma warning(disable: 4714),
awesome!  Who is the maintainer of variant anyways?

-- 
Frank