Skip to content

Conversation

j4m-can
Copy link

@j4m-can j4m-can commented Sep 2, 2022

There is no style setting to deal with continuations for a function
definition differently than other continuations. As is,
CONTINUATION_INDENT_WIDTH is uniformly applied. A new setting,
FUNCTION_CONTINUATION_INDENT_WIDTH, allows for function definition
continuations to be indented differently. For example, 8 spaces
instead of the common 4 sets off the definition continuation more
clearly. The default is to use CONTINUATION_INDENT_WIDTH otherwise.

There is no style setting to deal with continuations for a function
definition differently than other continuations. As is,
CONTINUATION_INDENT_WIDTH is uniformly applied. A new setting,
FUNCTION_CONTINUATION_INDENT_WIDTH, allows for function definition
continuations to be indented differently. For example, 8 spaces
instead of the common 4 sets off the definition continuation more
clearly. The default is to use CONTINUATION_INDENT_WIDTH otherwise.
@google-cla
Copy link

google-cla bot commented Sep 2, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant