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:21 PM Frank Mori Hess <[email protected]> > wrote: > > > > On Mon, Sep 19, 2022 at 3:16 AM Gavin Lambert via Boost-users > > <[email protected]> wrote: > > > > > >,struct boost::mpl::l_iter<struct boost::mpl::l_end> > *)' > > > marked as __forceinline not inlined > > > > > > I'm not sure whether the Real Bug™ is in signals2 or in variant, but > > > I don't think it's in any of my code since it doesn't name any of my > > > types above that I can see. > > > > The problem is not in signals2, as it makes no direct use of > > __forceinline. variant does make use of BOOST_FORCEINLINE so it > > probably needs to have the pragma suppression added somewhere. > > > > Actually, maybe the easiest thing would be to just put the pragma suppression > in the header that defines BOOST_FORCEINLINE (config/detail/suffix.hpp). 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. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost