787891a388
- 5140470240e110cdad301446124b2e6075c4034a Fix typos in the Abseil issue template. by Shaindel Schwartz <shaindel@google.com> - 97a197521aa13fed099483c5424be1d4d8a87add Removing deprecated internal interfaces from FixedArray. by Daniel Katz <katzdm@google.com> - 2a222b425752e696db5c1688f1dfdb17e228cae9 Rollback for test breakage. by Andrew Hunter <ahh@google.com> - d2d27e3ff67021b85726c1fc4d1d18b15e648ecf use std::allocator, not ::operator new in FixedArray for ... by Andrew Hunter <ahh@google.com> - 8e0c0a9f5e29e00e0dfca707b88741a7546d09d6 No need to test defined(__has_warning) if not using it by Abseil Team <absl-team@google.com> GitOrigin-RevId: 5140470240e110cdad301446124b2e6075c4034a Change-Id: I485aa818efa07f960c924edb62715b5cbc41b97b
1.1 KiB
Please submit a new Abseil Issue using the template below:
[Short title of proposed API change(s)]
Background
[Provide the background information that is required in order to evaluate the proposed API changes. No controversial claims should be made here. If there are design constraints that need to be considered, they should be presented here along with justification for those constraints. Linking to other docs is good, but please keep the pertinent information as self contained as possible in this section.]
Proposed API Change (s)
[Please clearly describe the API change(s) being proposed. If multiple changes, please keep them clearly distinguished. When possible, use example code snippets to illustrate before–after API usages. List pros-n-cons. Highlight the main questions that you want to be answered. Given the Abseil project compatibility requirements, describe why the API change is safe.]