maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Sync some doc changes ClangFormatStyleOptions.rst with doc comments in `Format.h` 

Summary:
These changes were corrected directly in ClangFormatStyleOptions.rst (llvm-svn: 350192 and llvm-svn: 351976) but these sections can be produced automatically using `dump_format_style.py` so sync the corresponding doc comments in `Format.h` as well.

Patch by Ronald Wampler

Reviewers: eugene, sylvestre.ledru, djasper

Reviewed By: sylvestre.ledru

Subscribers: jdoerfert, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58186

llvm-svn: 356842
This commit is contained in:
Sylvestre Ledru 2019-03-23 17:57:31 +00:00
parent 1466e5c383
commit d53135767d
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
clang/include/clang/Format/Format.h
View File

@ -1201,7 +1201,7 @@ struct FormatStyle {
/// A vector of prefixes ordered by the desired groups for Java imports.
///
/// Each group is seperated by a newline. Static imports will also follow the
/// Each group is separated by a newline. Static imports will also follow the
/// same grouping convention above all non-static imports. One group's prefix
/// can be a subset of another - the longest prefix is always matched. Within
/// a group, the imports are ordered lexicographically.

4
clang/include/clang/Tooling/Inclusions/IncludeStyle.h
View File

@ -67,7 +67,7 @@ struct IncludeStyle {
/// used for ordering ``#includes``.
///
/// `POSIX extended
/// <http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html>`_
/// <https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html>`_
/// regular expressions are supported.
///
/// These regular expressions are matched against the filename of an include
@ -79,7 +79,7 @@ struct IncludeStyle {
/// If none of the regular expressions match, INT_MAX is assigned as
/// category. The main header for a source file automatically gets category 0.
/// so that it is generally kept at the beginning of the ``#includes``
/// (http://llvm.org/docs/CodingStandards.html#include-style). However, you
/// (https://llvm.org/docs/CodingStandards.html#include-style). However, you
/// can also assign negative priorities if you have certain headers that
/// always need to be first.
///