2017-09-27 05:32:45 +02:00
|
|
|
|
Please submit a new Abseil Issue using the template below:
|
2017-09-19 22:54:40 +02:00
|
|
|
|
|
|
|
|
|
|
## [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."]
|
