a4cb1c8ba6
-- 6fdf24a197b964f9bacbebd0ceca305aef1654fc by Shaindel Schwartz <shaindel@google.com>: Internal change PiperOrigin-RevId: 231627312 -- 65f7faf52bff01384171efb85fee159378dedf70 by CJ Johnson <johnsoncj@google.com>: Relocates the definitions of the InputIterator-accepting parts of the InlinedVector API into the top-level. The removed functions had no other callers so there was no reason to keep the layer of indirection in the form of the function call. PiperOrigin-RevId: 231527459 -- 30e105b749b5ecc50fdaf26c7da589617efce425 by CJ Johnson <johnsoncj@google.com>: Relocates closing brace for absl namespace in InlinedVector to the correct end location PiperOrigin-RevId: 231477871 -- 063c1e8b9d1f032662c46d574e20ecc357b87d0c by Eric Fiselier <ericwf@google.com>: Cleanup std::hash probing metafunctions. Previously there were two different ways to probe for std::hash. One in hash.h and another in type_traits.h, and they were both implemented differently, and neither correctly worked around bad STL implementations. This patch unifies the implementations into a single IsHashable trait. It also: * Correctly checks for old libc++ versions where this won't work. * Avoids undefined behavior which resulted from calling std::is_constructible incomplete types. * Unifies the feature test macro used in the headers and the tests. Additionally it also slightly changes the behavior of when absl::variant is hashable. Previously we disable hashing when std::hash<T>()(key) was formed but when std::hash<T> couldn't be destructed. This seems wrong. If a user provides a evil specialization of std::hash, then it's OK for variant's hash to blow up. PiperOrigin-RevId: 231468345 -- 05d75dd4b07c893de9b104731644d0d207b01253 by Abseil Team <absl-team@google.com>: Import of CCTZ from GitHub. PiperOrigin-RevId: 231397518 -- a0ee9032f9e04039f3410ed17fcf45ae1a3868f5 by CJ Johnson <johnsoncj@google.com>: Remove unused EnableIfAtLeastInputIterator from InlinedVector PiperOrigin-RevId: 231348903 -- 4dcd4e9a6780a81d7a6974c7bf22a037e6482b49 by Abseil Team <absl-team@google.com>: Remove unnecessary register keyword from absl/base/internal/endian.h. PiperOrigin-RevId: 231316570 -- c8584836caa3a10f90a8604a85d4b831310b72ee by Abseil Team <absl-team@google.com>: Fix hashtablez_sampler compilation on older Android NDK builds PiperOrigin-RevId: 231283542 GitOrigin-RevId: 6fdf24a197b964f9bacbebd0ceca305aef1654fc Change-Id: I185b12fb8347e3ad0ffcb2cbb83a53450e5eb938 |
||
---|---|---|
absl | ||
CMake | ||
.clang-format | ||
.gitignore | ||
ABSEIL_ISSUE_TEMPLATE.md | ||
AUTHORS | ||
CMakeLists.txt | ||
conanfile.py | ||
CONTRIBUTING.md | ||
LICENSE | ||
LTS.md | ||
README.md | ||
UPGRADES.md | ||
WORKSPACE |
Abseil - C++ Common Libraries
The repository contains the Abseil C++ library code. Abseil is an open-source collection of C++ code (compliant to C++11) designed to augment the C++ standard library.
Table of Contents
About Abseil
Abseil is an open-source collection of C++ library code designed to augment the C++ standard library. The Abseil library code is collected from Google's own C++ code base, has been extensively tested and used in production, and is the same code we depend on in our daily coding lives.
In some cases, Abseil provides pieces missing from the C++ standard; in others, Abseil provides alternatives to the standard for special needs we've found through usage in the Google code base. We denote those cases clearly within the library code we provide you.
Abseil is not meant to be a competitor to the standard library; we've just found that many of these utilities serve a purpose within our code base, and we now want to provide those resources to the C++ community as a whole.
Quickstart
If you want to just get started, make sure you at least run through the Abseil Quickstart. The Quickstart contains information about setting up your development environment, downloading the Abseil code, running tests, and getting a simple binary working.
Building Abseil
Bazel is the official build system for Abseil, which is supported on most major platforms (Linux, Windows, MacOS, for example) and compilers. See the quickstart for more information on building Abseil using the Bazel build system.
If you require CMake support, please check the CMake build instructions.
Codemap
Abseil contains the following C++ library components:
base
Abseil Fundamentals
Thebase
library contains initialization code and other code which all other Abseil code depends on. Code withinbase
may not depend on any other code (other than the C++ standard library).algorithm
Thealgorithm
library contains additions to the C++<algorithm>
library and container-based versions of such algorithms.container
Thecontainer
library contains additional STL-style containers, including Abseil's unordered "Swiss table" containers.debugging
Thedebugging
library contains code useful for enabling leak checks, and stacktrace and symbolization utilities.hash
Thehash
library contains the hashing framework and default hash functor implementations for hashable types in Abseil.memory
Thememory
library contains C++11-compatible versions ofstd::make_unique()
and related memory management facilities.meta
Themeta
library contains C++11-compatible versions of type checks available within C++14 and C++17 versions of the C++<type_traits>
library.numeric
Thenumeric
library contains C++11-compatible 128-bit integers.strings
Thestrings
library contains a variety of strings routines and utilities, including a C++11-compatible version of the C++17std::string_view
type.synchronization
Thesynchronization
library contains concurrency primitives (Abseil'sabsl::Mutex
class, an alternative tostd::mutex
) and a variety of synchronization abstractions.time
Thetime
library contains abstractions for computing with absolute points in time, durations of time, and formatting and parsing time within time zones.types
Thetypes
library contains non-container utility types, like a C++11-compatible version of the C++17std::optional
type.utility
Theutility
library contains utility and helper code.
License
The Abseil C++ library is licensed under the terms of the Apache license. See LICENSE for more information.
Links
For more information about Abseil:
- Consult our Abseil Introduction
- Read Why Adopt Abseil to understand our design philosophy.
- Peruse our Abseil Compatibility Guarantees to understand both what we promise to you, and what we expect of you in return.