0ec11bad6f
- 06abebb2bdb201c572da209fc7f781d6bd774d6b Documentation fixes for `absl::optional`. by Abseil Team <absl-team@google.com> - 42adc4c4daade2e070dc337e94d8851a1fd4bead Rolling back the previous change because `__has_warning`... by Xiaoyi Zhang <zhangxy@google.com> - 02a42cbaa97d82ee7942bc498538359185d75087 Remove literal UTF8 strings in abseil code to avoid file ... by Jon Cohen <cohenjon@google.com> GitOrigin-RevId: 06abebb2bdb201c572da209fc7f781d6bd774d6b Change-Id: I4f4659c2e7ca6fc585b6c089bcf20ca61aced75d
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.]