diff options
| author | Dániel Szoboszlay <[email protected]> | 2016-05-13 23:05:23 +0200 |
|---|---|---|
| committer | Dan Gudmundsson <[email protected]> | 2016-05-18 10:12:49 +0200 |
| commit | c8b3e3a977bd8b4071e190c7c7aaa72f934af60a (patch) | |
| tree | 2e457633d8e50bf20a18b957dacd0932bb6f1950 /otp_build | |
| parent | 4fba4b14c4f9aa03294d8d187fe0dd1202744e82 (diff) | |
| download | otp-c8b3e3a977bd8b4071e190c7c7aaa72f934af60a.tar.gz otp-c8b3e3a977bd8b4071e190c7c7aaa72f934af60a.tar.bz2 otp-c8b3e3a977bd8b4071e190c7c7aaa72f934af60a.zip | |
Fix line-initial commas' indentation in type specs
Inside type specs, line-initial commas shall align with open curly
braces. This also applies to record definitions with type specs for
the fields.
For example:
-type foo() :: { a :: integer()
, b :: integer()
}.
For type specs for functions, the commas shall align with the opening
parenthese. So do a closing parenthese when put on a new line.
For example:
-spec foo( X :: integer()
, Y :: integer()
) -> integer().
This does not affect coding styles that don't put commas at the
beginning of lines.
Diffstat (limited to 'otp_build')
0 files changed, 0 insertions, 0 deletions