boost_intrusive

T

SiggyBar 92d6e58bb7 Fix empty control statement warnings

This change replaces code like this:
      if(safemode_or_autounlink)
         BOOST_INTRUSIVE_SAFE_HOOK_DEFAULT_ASSERT(node_algorithms::unique(to_insert));

with:
      BOOST_INTRUSIVE_SAFE_HOOK_DEFAULT_ASSERT(!safemode_or_autounlink || node_algorithms::unique(to_insert));

The reason for this change is that the first form generates
a warning for Visual C++ 14.1 in builds without asserts:
warning C4390: ';': empty controlled statement found; is this the intent?

Before this change the code was using a mix of the two forms
when invoking the BOOST_INTRUSIVE_SAFE_HOOK_DEFAULT_ASSERT()
and BOOST_INTRUSIVE_INVARIANT_ASSERT() macros.  Now it
consistently uses the second form.

2020-02-07 10:46:55 +01:00

doc

Fixes #46 : ("UB due to union based type punning")

2020-01-16 16:10:03 +01:00

example

Fix clang 6.0 warnings in tests: unused members, suspicious return types

2018-09-18 14:26:31 +02:00

include/boost/intrusive

Fix empty control statement warnings

2020-02-07 10:46:55 +01:00