There is an alternative approach. These warnings could be documented on the Boost website so that users can look them up for themselves and be advised what action, if any, they need take. (In most cases, this would be "this warning can be safely ignored - no action on the programmer's part is required"). There would be a section for each compiler for which Boost is available. This would require quite a lot of work, of course, but it would help put users' minds at rest and would not require any changes to be made to the code. Apart from the effort involved, the only other drawback I see is warnings might not come to light until Boost libraries are actually used, or might depend on the way the library is used. Perhaps, in that case, there could be an option for users to make requests about the severity of warnings as and when they encountered them, and for a record of them to be built up on the site in this way. No doubt a poll of the posters to this list ("What warnings in Boost code does your compiler give when you compile code using Boost libraries?") would go some way to getting it started. I don't know how practical this is, but it's an idea that might be worth considering.