Master list of macro and symbol collision issue reports in all Boost libraries

Hopefully github will draw a line through each of these as/if they get closed so one can see an overview of progress. When/if they are all closed, build tooling ought to add a build-time check to prevent breakage of Boost library guidelines in the future.

- ~https://github.com/boostorg/container/issues/136~
- https://github.com/boostorg/date_time/issues/118
- ~https://github.com/boostorg/exception/issues/28~
- https://github.com/boostorg/fusion/issues/218
- ~https://github.com/boostorg/gil/issues/410~
- ~https://github.com/boostorg/graph/issues/193~
- ~https://github.com/boostorg/iterator/issues/53~
- ~https://github.com/boostorg/lambda/issues/18~
- ~https://github.com/boostorg/math/issues/278~
- ~https://github.com/boostorg/multi_array/issues/25~
- ~https://github.com/boostorg/parameter/issues/94~
- https://github.com/boostorg/phoenix/issues/90
- ~https://github.com/boostorg/polygon/issues/33~
- https://github.com/boostorg/program_options/issues/88
- ~https://github.com/boostorg/property_map/issues/12~
- https://github.com/boostorg/python/issues/281
- ~https://github.com/boostorg/qvm/issues/22~
- ~https://github.com/boostorg/serialization/issues/185~
- https://github.com/boostorg/spirit/issues/562
- ~https://github.com/boostorg/stacktrace/issues/85~
- https://github.com/boostorg/thread/issues/302
- https://github.com/boostorg/type_traits/issues/135
- ~https://github.com/boostorg/wave/issues/52~