Skip to content

A
abseil-cpp
Switch branch/tag
  1. 29 Aug, 2023 2 commits
    • Make raw_hash_set::destroy_slots no longer public. It was never meant to be a… · e3fb72ff 
      Make raw_hash_set::destroy_slots no longer public. It was never meant to be a public member of the API.

PiperOrigin-RevId: 561061460
Change-Id: Ib804d3d3cf427ebfc9e622db9915287eb8045e26
      Evan Brown committed
    • Remove the legacy thread annotation spellings · ba7a9e24 
      The legacy thread annotations were spellings that were not prefixed
with ABSL_ and caused conflicts with other libraries. These spellings
have been removed by default for a while, but could have been added
back with the temporary compile flag
-DABSL_LEGACY_THREAD_ANNOTATIONS. This change completely removes the
legacy spellings.

If you were relying on the legacy spellings, the fix is
straightforward. Simply add the ABSL_ prefix. For example,
GUARDED_BY() becomes ABSL_GUARDED_BY().

PiperOrigin-RevId: 560874026
Change-Id: Id072e67435472220ea4f43ccbf267028c13feba7
      Derek Mauro committed
  3. 28 Aug, 2023 1 commit
    • Implement ABSL_ATTRIBUTE_PURE_FUNCTION and ABSL_ATTRIBUTE_CONST_FUNCTION · 1d83ac71 
      Pure functions have no effects except to return a value, and their
return value depends only on the parameters and global
variables. Functions of this kind can be subject to data flow analysis
and might be eliminated. In practice, this means that repeated calls
to the same function with the same arguments may be optimized away and
only evaluated once.

Const functions are similar to pure functions, but may not depend on
global variables at all.

It is an error not to use the result of a function with one of these
attributes, since these functions have no other visible effects.

Since some Abseil functions are tagged with these attributes, this is
potentially a breaking change for code that doesn't use the result of
these functions.

For example, absl::Minutes() is tagged with
ABSL_ATTRIBUTE_CONST_FUNCTION.  If, for example, the result of
absl::Minutes(n) is unused, some compilers with issue a warning or
error. If this is the case, it is likely that there is a typo in the
code, or the call can be removed.
PiperOrigin-RevId: 560803581
Change-Id: Icd6f218be2cfb7226f8ab6b2d97cd960c0d3d72f
      Derek Mauro committed
  5. 25 Aug, 2023 1 commit
  7. 23 Aug, 2023 2 commits
  9. 21 Aug, 2023 2 commits
  11. 18 Aug, 2023 1 commit
    • Check CRC cordrep child nodes for nullptr. · 94b37802 
      Some time ago the invariant for CRC cordreps was relaxed to allow for nullptr values on empty cords with an explicit empty CRC value. The CordzInfo analysis never checked for nullptr values causing cord sampling to crash if the sampling happened to include a (very unlikely) empty Cord value.

PiperOrigin-RevId: 558202613
Change-Id: Ib0e1eadd08047167e4df5d3035b36dca2c285a0d
      Martijn Vels committed
  13. 17 Aug, 2023 4 commits
  15. 16 Aug, 2023 3 commits
  17. 15 Aug, 2023 3 commits
  19. 14 Aug, 2023 3 commits
  21. 11 Aug, 2023 2 commits
  23. 10 Aug, 2023 4 commits
  25. 09 Aug, 2023 2 commits
  27. 08 Aug, 2023 7 commits
  29. 07 Aug, 2023 2 commits
  31. 04 Aug, 2023 1 commit