Re: [Boost-users] [signals2][variant] inline warning with MSVC 2022
Peter Dimov via Boost <[email protected]>
| Newsgroups | gmane.comp.lib.boost.devel,gmane.comp.lib.boost.user |
|---|---|
| Message-ID | <[email protected]> |
Frank Mori Hess wrote: > On Wed, Sep 21, 2022 at 12:32 PM Peter Dimov <[email protected]> > wrote: > > > > 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. 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. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost