Closed joaquintides closed 1 year ago
Why are the warning restore pragmas not in reverse order of the suppression ones?
Merging #176 (200c0c6) into develop (6be2bf8) will increase coverage by
0.04%
. The diff coverage is99.23%
.:exclamation: Current head 200c0c6 differs from pull request most recent head 91eddba. Consider uploading reports for the commit 91eddba to get more accurate results
Why are the warning restore pragmas not in reverse order of the suppression ones?
I opted for having those pragmas be mutually exclusive (note the #elif
s), hence restore order can't be reverse (some branches are true simultaneously).
Restores
boost::unordered_flat_[map|set]
's allocator awareness by restrictingstd::memcpy
-based element copy tostd::allocator
and allocators without a suitableconstruct
memfun.