klimek added inline comments.
Comment at: lib/Sema/SemaCodeComplete.cpp:2411-2412
+ if (DefValue.at(0) != '=') {
+// If we don't have = in front of value
+return " = " + DefValue;
+ }
Can you expand in the comment on when each of these happens?
klimek added a comment.
Specifically, ping Richard for new top-level lib in clang.
https://reviews.llvm.org/D34512
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
klimek added a comment.
In https://reviews.llvm.org/D34512#800626, @whisperity wrote:
> In https://reviews.llvm.org/D34512#800502, @xazax.hun wrote:
>
> > In https://reviews.llvm.org/D34512#800499, @klimek wrote:
> >
> > > In https://reviews.llvm.org/D34512#800490, @xazax.hun wrote:
> > >
> > >
klimek added a reviewer: rsmith.
klimek added a comment.
+Richard as top-level code owner for new libs.
For bikeshedding the name: I'd have liked libIndex, but that's already taken.
CrossTU doesn't seem too bad to me, too, though.
https://reviews.llvm.org/D34512
klimek added a comment.
In https://reviews.llvm.org/D34512#800490, @xazax.hun wrote:
> It looks like Richard approved libTooling as a dependency for clang on the
> mailing list (http://lists.llvm.org/pipermail/cfe-dev/2017-July/054536.html).
> If it is ok to have this code in libTooling (for
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
Repository:
rL LLVM
https://reviews.llvm.org/D34696
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
LG, thx for bearing with me, this looks great.
(and sorry if I didn't send this earlier, just noticed I forgot to hit submit
:( )
Comment at:
klimek added a comment.
In https://reviews.llvm.org/D34696#795020, @arphaman wrote:
> In https://reviews.llvm.org/D34696#793613, @klimek wrote:
>
> > The main thing I'm concerned about is having the main code in core, but
> > having all tests in tools-extra. I think if we go that route we
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D34755
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
The main thing I'm concerned about is having the main code in core, but having
all tests in tools-extra. I think if we go that route we should also move
clang-rename and its tests to core. Thoughts?
Repository:
rL LLVM
https://reviews.llvm.org/D34696
klimek added a comment.
In https://reviews.llvm.org/D33644#793601, @yvvan wrote:
> In https://reviews.llvm.org/D33644#793594, @klimek wrote:
>
> > In https://reviews.llvm.org/D33644#793577, @yvvan wrote:
> >
> > > In https://reviews.llvm.org/D33644#793573, @klimek wrote:
> > >
> > > > In
klimek added a comment.
In https://reviews.llvm.org/D33644#793577, @yvvan wrote:
> In https://reviews.llvm.org/D33644#793573, @klimek wrote:
>
> > In https://reviews.llvm.org/D33644#783903, @yvvan wrote:
> >
> > > Do not evaluate numbers.
> > > Check for != "=" is needed not to mess with
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
Repository:
rL LLVM
https://reviews.llvm.org/D34687
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a reviewer: rsmith.
klimek added a comment.
Richard (added as reviewer) usually owns decisions around clang itself. Writing
an email to cfe-dev with the numbers and wait for whether others have concerns
would probably also be good.
https://reviews.llvm.org/D30691
klimek added inline comments.
Comment at: include/clang/Tooling/CrossTranslationUnit.h:53-58
+ /// \p CrossTUDir directory, called \p IndexName. In case the declaration is
+ /// found in the index the corresponding AST file will be loaded and the
+ /// definition of the
klimek added reviewers: dexonsmith, akyrtzi, benlangmuir, arphaman.
klimek added a comment.
Adding folks interested in the indexing discussion.
Comment at: include/clang/Tooling/CrossTranslationUnit.h:53-58
+ /// \p CrossTUDir directory, called \p IndexName. In case the
klimek added a comment.
In https://reviews.llvm.org/D34304#788080, @saugustine wrote:
> In https://reviews.llvm.org/D34304#787699, @klimek wrote:
>
> > I mean, arguments need to be adjusted before converting to ArgStringList
> > and calling newInvocation? I'm not sure I fully understand the
klimek added a comment.
General direction looks good.
I think in addition to integration tests through the static analyzer, we should
still have unit tests.
Comment at: include/clang/Tooling/CrossTranslationUnit.h:47
+
+ const FunctionDecl *getCTUDefinition(const
klimek added inline comments.
Comment at: include/clang/Tooling/ASTDiff/ASTDiff.h:57
+/// Within a tree, this identifies a node by its preorder offset.
+using NodeId = int;
+
johannes wrote:
> arphaman wrote:
> > I think that it's better to make make `NodeId` a
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
LG
https://reviews.llvm.org/D34469
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
LG
https://reviews.llvm.org/D34470
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
I mean, arguments need to be adjusted before converting to ArgStringList and
calling newInvocation? I'm not sure I fully understand the problem, can you
elaborate?
https://reviews.llvm.org/D34304
___
cfe-commits mailing
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D33823
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D34287
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
Reviewing this mainly from the API view, and leaving the technical details to
others :)
Comment at: include/clang/Tooling/ASTDiff/ASTDiff.h:124
+
+class ASTDiff {
+ TreeRoot ,
Generally, can we put the public interface first in the
klimek added inline comments.
Comment at: include/clang/Frontend/PrecompiledPreamble.h:124
+/// CanReusePreamble + AddImplicitPreamble to make use of it.
+class PrecompiledPreamble {
+public:
ilya-biryukov wrote:
> klimek wrote:
> > If a user doesn't care about
klimek added inline comments.
Comment at: lib/Frontend/ASTUnit.cpp:131-136
+/// \brief Get a source buffer for \p MainFilePath, handling all file-to-file
+/// and file-to-buffer remappings inside \p Invocation.
+static PossiblyOwnedBuffer
+getBufferForFileHandlingRemapping(const
klimek added a comment.
In https://reviews.llvm.org/D34263#784168, @akyrtzi wrote:
> In https://reviews.llvm.org/D34263#783694, @klimek wrote:
>
> > how many patches for single file mode are coming down the road, though? I'm
> > somewhat concerned about the overall complexity it'll add to
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
oh, and lg from my side
https://reviews.llvm.org/D34263
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
In https://reviews.llvm.org/D34304#784496, @saugustine wrote:
> In https://reviews.llvm.org/D34304#783675, @klimek wrote:
>
> > I think a better way might be to generally leave dependency options alone,
> > add a default argument adapter to filter out all deps related
klimek added inline comments.
Comment at: include/clang/Tooling/ASTDiff/ASTDiff.h:123
+
+void runDiff(ASTContext , ASTContext );
+
This is the main exposed interface?
Generally, if all we want to do is printing, I wouldn't put that into a library
in Tooling,
klimek added inline comments.
Comment at: lib/Sema/SemaCodeComplete.cpp:2453
std::string PlaceholderStr = FormatFunctionParameter(Policy, Param);
+if (Param->hasDefaultArg() && PlaceholderStr.find("=") ==
std::string::npos) {
+std::string DefaultValue =
klimek added inline comments.
Comment at: lib/Format/UsingDeclarationsSorter.cpp:41-42
+
+bool computeUsingDeclarationLabel(const FormatToken *UsingTok,
+ std::string *Label) {
+ assert(UsingTok && UsingTok->is(tok::kw_using) && "Expecting a
klimek added inline comments.
Comment at: include/clang/Frontend/PrecompiledPreamble.h:42-43
+/// destructors.
+/// An assertion will fire if two PCHTempFiles are created with the same name,
+/// so it's not intended to be used outside preamble-handling.
+class TempPCHFile {
klimek added a comment.
Generally this patch lg from my side - how many patches for single file mode
are coming down the road, though? I'm somewhat concerned about the overall
complexity it'll add to clang.
When I saw your first patch my reaction was "wow, this works with this little
change -
klimek added a comment.
I think a better way might be to generally leave dependency options alone, add
a default argument adapter to filter out all deps related flags, and allow
users to add their own argument adapters that don't do that.
https://reviews.llvm.org/D34304
klimek added inline comments.
Comment at: lib/Sema/SemaCodeComplete.cpp:2453
std::string PlaceholderStr = FormatFunctionParameter(Policy, Param);
+if (Param->hasDefaultArg() && PlaceholderStr.find("=") ==
std::string::npos) {
+std::string DefaultValue =
klimek added a comment.
Ok, now I get it - can you please add tests? This is usually tested by adding a
c-index-test based test.
Comment at: lib/Sema/SemaCodeComplete.cpp:2411-2417
+ const SourceLocation StartLoc = SrcRange.getBegin();
+ const SourceLocation EndLoc =
klimek added a comment.
Can you give a bit more background what this is trying to do?
https://reviews.llvm.org/D33644
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
klimek added a comment.
Generally LG from my side.
Comment at: unittests/Format/FormatTest.cpp:1363-1381
+ EXPECT_EQ("namespace {\n"
+ "namespace {\n"
+"}} // namespace
klimek added a comment.
In https://reviews.llvm.org/D32480#773807, @Typz wrote:
> So how do I proceed?
>
> 1. Keep the CompactNamespace option, and make "compacted" namespaces always
> add at most one level of indentation
> 2. Or assume that this can only ever usefully work with the behavior of
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
Apart from fixme LG.
Comment at: lib/Format/UnwrappedLineParser.cpp:397
// blocks (for example while parsing lambdas).
+ // TODO(martinprobst): Some of
klimek added a comment.
I'm less concerned about everything suddenly re-indenting when you change code
- if you use any kind of namespace indentation, that's what will happen now and
then (and is why many style guides do not indent in namespaces).
For what it's worth, I'd
1. vote for only
klimek added inline comments.
Comment at: clangd/ClangdLSPServer.h:23
+
+class ClangdLSPServer {
+ class LSPDiagnosticsConsumer;
ilya-biryukov wrote:
> klimek wrote:
> > I'd have expected something that's called LSP server to work on the LSP
> > protocol level
klimek added inline comments.
Comment at: clangd/ClangdLSPServer.h:23
+
+class ClangdLSPServer {
+ class LSPDiagnosticsConsumer;
I'd have expected something that's called LSP server to work on the LSP
protocol level (that is, have a server(iostream) equivalent
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D32909
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
Is there a specific reason to take this out? It seems generally useful to allow
compilation-db implementors to provide sources.
https://reviews.llvm.org/D32351
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
In https://reviews.llvm.org/D31992#725912, @malaperle-ericsson wrote:
> In https://reviews.llvm.org/D31992#725866, @krasimir wrote:
>
> > Seems that we're starting to hit some YAML/JSON mismatches, or is it that
> > your YAML string support is lacking?
>
>
> I don't
klimek added inline comments.
Comment at: clangd/Protocol.cpp:26-50
+ for (llvm::StringRef::iterator i = Input.begin(), e = Input.end(); i != e;
++i) {
+if (*i == '\\')
+ EscapedInput += "";
+else if (*i == '"')
+ EscapedInput += "\\\"";
+// bell
+
klimek added inline comments.
Comment at: include/clang/Tooling/Refactoring/AtomicChange.h:129
+struct ApplyChangesSpec {
+ // If true, cleans up redundant/erroneous around changed code with
+ // clang-format's cleanup functionality, e.g. redundant commas around deleted
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D30735
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
In https://reviews.llvm.org/D30650#693165, @Eugene.Zelenko wrote:
> I think we should refactor this check as part of Static Analyzer, since it's
> path-sensitive.
Are you saying it should be path sensitive? Because currently it's not, right?
klimek added a comment.
Is the diff view on phab broken, or am I missing something? I only see a single
line of diff now, and don't see a way to change the diff.
https://reviews.llvm.org/D27810
___
cfe-commits mailing list
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D30636
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added inline comments.
Comment at: docs/ClangFormatStyleOptions.rst:218
+
+#define A \
+int ; \
Do we really align these 3 spaces out?
Comment at: docs/ClangFormatStyleOptions.rst:447
+ SomeClass::Constructor()
+
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D27054
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a comment.
Also, do we want to not call ReplaceFile in Path.inc on Win if it potentially
leaves temp files lying around?
Reading the code, it looks like we currently actually believe it may fail, and
retry with MoveFileEx afterwards...
https://reviews.llvm.org/D30385
klimek added a comment.
Can we open the files with FILE_SHARE_DELETE instead?
https://reviews.llvm.org/D30385
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
klimek added inline comments.
Comment at: include/clang/Rewrite/Core/Rewriter.h:188-197
+ /// prewrite(FID) is called after all changes to FID have been written to a
+ /// temporary file, but before that temporary file is moved into FID's
+ /// location. Windows's
klimek added inline comments.
Comment at: include-fixer/find-all-symbols/FindAllSymbols.cpp:251
+ } else {
+assert(false && "Must match a NamedDecl!");
+ }
You can use llvm_unreachable instead. Or do you actually want to fall through
in release mode?
klimek added inline comments.
Comment at: test/Format/check-coding-style-mozilla.cpp:7-9
+/* This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D29943
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added inline comments.
Comment at: lib/Format/BreakableToken.cpp:397
+//
+// Don't try aligning if there are less lines, since some patterns like
+//
fewer lines
Comment at: lib/Format/BreakableToken.cpp:402
+
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
Comment at: clangd/ASTManager.cpp:138-139
+ // Currently we discard all pending requests and just enqueue the latest one.
+ while (!RequestQueue.empty())
+
klimek added inline comments.
Comment at: clangd/ASTManager.h:67
+ /// Setting Done to true will make the worker thread terminate.
+ std::atomic Done;
+};
bkramer wrote:
> klimek wrote:
> > arphaman wrote:
> > > It looks like `Done` is always accessed in a
klimek added inline comments.
Comment at: clangd/ASTManager.cpp:69
+ // our one-element queue is empty.
+ if (!RequestIsPending && !Done)
+ClangRequestCV.wait(Lock);
arphaman wrote:
> This is just a suggestion based on personal opinion:
klimek added inline comments.
Comment at: lib/Basic/FileManager.cpp:167-168
DirNameStr = DirName.str() + '.';
+llvm::sys::path::native(DirNameStr);
+DirName = DirNameStr;
+ } else {
I'd add a canonicalizePath function that:
-> on unix just returns
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg.
I'd probably still call it consumeComments or something, as we require a flush
afterwards for the unconsumed comments, but I don't feel too strongly about
that.
klimek added inline comments.
Comment at: lib/Format/UnwrappedLineParser.h:121-123
+ // Comments specifies the sequence of comment tokens to analyze. They get
+ // either pushed to the current line or added to the comments before the next
+ // token.
krasimir
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D29699
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added inline comments.
Comment at: lib/Format/UnwrappedLineParser.h:121-123
+ // Comments specifies the sequence of comment tokens to analyze. They get
+ // either pushed to the current line or added to the comments before the next
+ // token.
krasimir
klimek added inline comments.
Comment at: lib/Format/UnwrappedLineParser.h:121-123
+ // Comments specifies the sequence of comment tokens to analyze. They get
+ // either pushed to the current line or added to the comments before the next
+ // token.
Given
klimek added inline comments.
Comment at: lib/Format/UnwrappedLineParser.cpp:2207-2208
+const FormatToken *NextTok) {
+ // Decides which comment tokens should be added to the current line and which
+ // should be added as comments before the next token.
+ //
klimek added a comment.
I think this looks pretty good. More comments would help :) Also, organize is
spelled with a 'z' in American.
https://reviews.llvm.org/D29626
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added a reviewer: hans.
klimek added a comment.
+hans
+1 to "format only current document but save all" not making much sense :)
Comment at: tools/clang-format-vs/ClangFormat/TypeConverterUtils.cs:7
+{
+public sealed class TypeConverterUtils
+{
klimek added inline comments.
Comment at: clang-query/QueryReplace.cpp:50
+
+void QueryReplaceTool::addOperation(clang::query::QueryReplaceSpec ) {
+ ast_matchers::dynamic::Diagnostics Diag;
Shouldn't that also just return the error?
Comment
klimek added inline comments.
Comment at: clangd/JSONRPCDispatcher.h:25-32
+ virtual ~Handler() = default;
+
+ /// Called when the server receives a method call. This is supposed to return
+ /// a result on Outs.
+ virtual void handleMethod(llvm::yaml::MappingNode *Params,
klimek accepted this revision.
klimek added a comment.
LG. Couple of questions.
Comment at: clangd/ClangDMain.cpp:65
+// Now read the JSON.
+std::vector JSON;
+JSON.resize(Len);
Adi wrote:
> Avoid unnecessary JSON.resize(Len) & potential
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg minus adding the FIXME to the place where we need the change.
Comment at: lib/Format/UnwrappedLineParser.cpp:2127-2129
+// Additional fine-grained breaking of line
klimek added a comment.
Generally looks like the right direction, minus that I'm not sure yet what the
plan for things broken in BreakableToken are.
Comment at: lib/Format/TokenAnnotator.cpp:1843
+Current->MatchingParen->opensBlockOrBlockTypeList(Style))
+
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
lg
https://reviews.llvm.org/D29271
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
LG
https://reviews.llvm.org/D28764
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added inline comments.
Comment at: lib/Format/BreakableToken.cpp:747
+Split SplitBefore, WhitespaceManager ) {
+ // If this is the first line of a token, we need to inform Whitespace Manager
+ // about it: either adapt the whitespace range preceding it, or mark it
klimek added inline comments.
Comment at: lib/Format/BreakableToken.cpp:279-280
+ return Content.size() >= 2 &&
+ Content != "clang-format on" &&
+ Content != "clang-format off" &&
+ !Content.endswith("\\") &&
Can we now use delimitsRegion here?
klimek added inline comments.
Comment at: lib/Format/BreakableToken.h:42-48
+/// There is a pair of operations that are used to compress a long whitespace
+/// range with a single space if that will bring the line lenght under the
+/// column limit:
+/// -
klimek added a comment.
This is starting to be pretty awesome. The one thing that would help me review
the gist of the implementation a bit more is if that had a bit more comments.
Perhaps go over the math in the code and put some comments in why we're doing
what at various steps.
klimek added inline comments.
Comment at: lib/Format/ContinuationIndenter.cpp:1158-1159
+CommentPragmasRegex.match(Current.TokenText.substr(2)) ||
+Current.TokenText.substr(2).ltrim().startswith("clang-format on") ||
+
klimek added inline comments.
Comment at: lib/Format/BreakableToken.h:55-56
+/// been reformatted, and
+/// - replaceWhitespaceBefore, for executing the reflow using a whitespace
+/// manager.
+///
Shouldn't that be called insertBreakBefore for consistency
klimek added inline comments.
Comment at: lib/Format/BreakableToken.h:40
+/// of the content after a split has been used for breaking, and
+/// - insertBreak, for executing the split using a whitespace manager.
+///
Do we want to describe how replaceWhitespace
This revision was automatically updated to reflect the committed changes.
Closed by commit rL291664: Improve include fixer's ranking by taking the paths
into account. (authored by klimek).
Changed prior to commit:
https://reviews.llvm.org/D28548?vs=83930=83937#toc
Repository:
rL LLVM
klimek created this revision.
klimek added a reviewer: bkramer.
klimek added a subscriber: cfe-commits.
Instead of just using popularity, we also take into account how similar the
path of the current file is to the path of the header.
Our first approach is to get popularity into a reasonably
klimek added a reviewer: bkramer.
klimek added a comment.
+benjamin
https://reviews.llvm.org/D28260
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
LG
https://reviews.llvm.org/D28465
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
klimek added inline comments.
Comment at: lib/Format/Format.cpp:1920-1922
+ std::error_code EC = FS->makeAbsolute(Path);
+ assert(!EC);
+ (void)EC;
amaiorano wrote:
> klimek wrote:
> > I think if makeAbsolute doesn't work, we will probably want to err out
klimek accepted this revision.
klimek added a comment.
This revision is now accepted and ready to land.
Apart from the error handling LG. Thanks!
Comment at: lib/Format/Format.cpp:1920-1922
+ std::error_code EC = FS->makeAbsolute(Path);
+ assert(!EC);
+ (void)EC;
klimek added a comment.
Why isn't the right solution to make getStyle() use vfs::FileSystem? Generally,
everything in clang-format (well, in clang) should use vfs::FileSystem for file
access.
https://reviews.llvm.org/D27971
___
cfe-commits
klimek added a comment.
In https://reviews.llvm.org/D27440#626477, @amaiorano wrote:
> In https://reviews.llvm.org/D27440#626415, @ioeric wrote:
>
> > `llvm::ErrorOr` carries `std::error_code`. If you want richer information
> > (e.g. error_code + error message), `llvm::Expcted` and
klimek added a reviewer: ioeric.
klimek added a comment.
+eric, who has some experience llvm::Error'ing our interfaces :)
llvm::ErrorOr seems like the right approach here?
https://reviews.llvm.org/D27440
___
cfe-commits mailing list
klimek added inline comments.
Comment at: lib/Format/ContinuationIndenter.cpp:1174-1175
LineIndex != EndIndex; ++LineIndex) {
-if (!DryRun)
- Token->replaceWhitespaceBefore(LineIndex, Whitespaces);
+Token->replaceWhitespaceBefore(LineIndex,
klimek added inline comments.
Comment at: lib/Format/BreakableToken.cpp:471
+ WhitespaceManager )
{
+ if (Tok.is(TT_LineComment)) {
+// If this is the first line of a token, inform Whitespace Manager about
it.
401 - 500 of 525 matches
Mail list logo