Is this entirely harmless again?
Quite possibly; you'd need to review the Boost internal code to find out. But in any case, if there is an issue, it's in Boost that this needs to be fixed.
Maybe I should just be configuring with --enable-suppress-external-warnings and ignoring all Boost warnings?
Unless you feel like debugging Boost itself, yes.
A signed integer shouldn't be compared to an unsigned integer though surely?
There is nothing inherently wrong with it. It's an indication that the code could be written in a more obviously correct way likely, but it's perfectly reasonable to encounter this in bug-free code. For example when in the context this is executed, it's known that the signed integer is never negative.
You can get bonuses upto $100 FREE BONUS when you:
💰 Install these recommended apps:
💲 SocialGood - 100% Crypto Back on Everyday Shopping
💲 xPortal - The DeFi For The Next Billion
💲 CryptoTab Browser - Lightweight, fast, and ready to mine!
💰 Register on these recommended exchanges:
🟡 Binance🟡 Bitfinex🟡 Bitmart🟡 Bittrex🟡 Bitget
🟡 CoinEx🟡 Crypto.com🟡 Gate.io🟡 Huobi🟡 Kucoin.
Comments