Re: [boost] [signals2][variant] inline warning with MSVC 2022
Frank Mori Hess via Boost-users <[email protected]>
| Newsgroups | gmane.comp.lib.boost.user,gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <CAJz5Opfk26ACzSGksj-0g5JP_RLd=R5gOXO2cvZL3XbSNNSykw@mail.gmail.com> |
On Thu, Sep 22, 2022 at 8:57 AM Peter Dimov <[email protected]> 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