On Wed, Sep 21, 2022 at 12:32 PM Peter Dimov <pdi...@gmail.com> 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. If the compiler is just going to treat it as a suggestion, I don't see the point of boost headers using it and then suppressing the warning. -- Frank _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
