GSL/.clang-format

ColumnLimit: 100

UseTab: Never
IndentWidth: 4
AccessModifierOffset: -4
NamespaceIndentation: Inner

BreakBeforeBraces: Allman
AlwaysBreakTemplateDeclarations: true
BreakConstructorInitializersBeforeComma: true
ConstructorInitializerAllOnOneLineOrOnePerLine: true
AllowShortBlocksOnASingleLine: true
AllowShortFunctionsOnASingleLine: All
AllowShortIfStatementsOnASingleLine: true
AllowShortLoopsOnASingleLine: true

PointerAlignment: Left
AlignConsecutiveAssignments: false
AlignTrailingComments: true

SpaceAfterCStyleCast: true
Add column limit to .clang-format 2015-10-01 20:53:37 -04:00			`ColumnLimit: 100`
Add .clang-format file To have any hope of achieving consistent formatting there needs to be a standard and a mechanism for enforcing it. This is a first step in that direction. This format specification is intended to mimic the existing style insofar as the current source has any consistent style. For example the determination as to whether ref qualifiers should bind to the type or variable name was made by trying both and seeing which produced fewer changes. One exception is the use of tabs vs. spaces, which was decided based on a comment by neilmacintosh [here][1]. To use clang-format with Visual Studio [download][2] and install the clang-format plugin. In VS ctrl-r, ctrl-f formats the current line or text selection. [1]: https://github.com/Microsoft/GSL/issues/55 [2]: http:llvm.org/builds/ 2015-09-26 18:00:54 -04:00
			`UseTab: Never`
			`IndentWidth: 4`
			`AccessModifierOffset: -4`
			`NamespaceIndentation: Inner`

			`BreakBeforeBraces: Allman`
Add column limit to .clang-format 2015-10-01 20:53:37 -04:00			`AlwaysBreakTemplateDeclarations: true`
Add .clang-format file To have any hope of achieving consistent formatting there needs to be a standard and a mechanism for enforcing it. This is a first step in that direction. This format specification is intended to mimic the existing style insofar as the current source has any consistent style. For example the determination as to whether ref qualifiers should bind to the type or variable name was made by trying both and seeing which produced fewer changes. One exception is the use of tabs vs. spaces, which was decided based on a comment by neilmacintosh [here][1]. To use clang-format with Visual Studio [download][2] and install the clang-format plugin. In VS ctrl-r, ctrl-f formats the current line or text selection. [1]: https://github.com/Microsoft/GSL/issues/55 [2]: http:llvm.org/builds/ 2015-09-26 18:00:54 -04:00			`BreakConstructorInitializersBeforeComma: true`
			`ConstructorInitializerAllOnOneLineOrOnePerLine: true`
			`AllowShortBlocksOnASingleLine: true`
			`AllowShortFunctionsOnASingleLine: All`
			`AllowShortIfStatementsOnASingleLine: true`
			`AllowShortLoopsOnASingleLine: true`

			`PointerAlignment: Left`
			`AlignConsecutiveAssignments: false`
Applied clang-format to the source. 2016-07-20 16:17:47 -04:00			`AlignTrailingComments: true`
Add .clang-format file To have any hope of achieving consistent formatting there needs to be a standard and a mechanism for enforcing it. This is a first step in that direction. This format specification is intended to mimic the existing style insofar as the current source has any consistent style. For example the determination as to whether ref qualifiers should bind to the type or variable name was made by trying both and seeing which produced fewer changes. One exception is the use of tabs vs. spaces, which was decided based on a comment by neilmacintosh [here][1]. To use clang-format with Visual Studio [download][2] and install the clang-format plugin. In VS ctrl-r, ctrl-f formats the current line or text selection. [1]: https://github.com/Microsoft/GSL/issues/55 [2]: http:llvm.org/builds/ 2015-09-26 18:00:54 -04:00
			`SpaceAfterCStyleCast: true`