By Alex Strelnikov, Abseil Engineer
As we promised when we released our Compatibility Guidelines, we have developed a process for announcing and handling any API-breaking changes we may need to make within the Abseil code base. Our C++ Automated Upgrade guide outlines this process, which consists of clang-tidy tooling and associated communication regarding the change. A list of all such tools will be listed on our Upgrade Tools page.
At this time, we are also releasing our first such tool: a clang-tidy check
removing bug-prone implicit conversions in calls to several
As outlined in our upgrade guide, we will always first serve notice of such a tool via this blog, and will also blog once we’ve officially removed the deprecated API.