Refactoring for for the internal command line completion API (NFC)
Summary:
This patch refactors the internal completion API. It now takes (as far as possible) a single
CompletionRequest object instead o half a dozen in/out/in-out parameters. The CompletionRequest
contains a common superset of the different parameters as far as it makes sense. This includes
the raw command line string and raw cursor position, which should make the `expr` command
possible to implement (at least without hacks that reconstruct the command line from the args).
This patch is not intended to change the observable behavior of lldb in any way. It's also as
minimal as possible and doesn't attempt to fix all the problems the API has.
Some Q&A:
Q: Why is this not fixing all the problems in the completion API?
A: Because is a blocker for the expr command completion which I want to get in ASAP. This is the
smallest patch that unblocks the expr completion patch and which allows trivial refactoring in the future.
The patch also doesn't really change the internal information flow in the API, so that hopefully
saves us from ever having to revert and resubmit this humongous patch.
Q: Can we merge all the copy-pasted code in the completion methods
(like computing the current incomplete arg) into CompletionRequest class?
A: Yes, but it's out of scope for this patch.
Q: Why the `word_complete = request.GetWordComplete(); ... ` pattern?
A: I don't want to add a getter that returns a reference to the internal integer. So we have
to use a temporary variable and the Getter/Setter instead. We don't throw exceptions
from what I can tell, so the behavior doesn't change.
Q: Why are we not owning the list of matches?
A: Because that's how the previous API works. But that should be fixed too (in another patch).
Q: Can we make the constructor simpler and compute some of the values from the plain command?
A: I think this works, but I rather want to have this in a follow up commit. Especially when making nested
request it's a bit awkward that the parsed arguments behave as both input/output (as we should in theory
propagate the changes on the nested request back to the parent request if we don't want to change the
behavior too much).
Q: Can't we pass one const request object and then just return another result object instead of mixing
them together in one in/out parameter?
A: It's hard to get keep the same behavior with that pattern, but I think we can also get a nice API with just
a single request object. If we make all input parameters read-only, we have a clear separation between what
is actually an input and what an output parameter (and hopefully we get rid of the in-out parameters).
Q: Can we throw out the 'match' variables that are not implemented according to the comment?
A: We currently just forward them as in the old code to the different methods, even though I think
they are really not used. We can easily remove and readd them once every single completion method just
takes a CompletionRequest, but for now I prefer NFC behavior from the perspective of the API user.
Reviewers: davide, jingham, labath
Reviewed By: jingham
Subscribers: mgorny, friss, lldb-commits
Differential Revision: https://reviews.llvm.org/D48796
llvm-svn: 336146
2018-07-03 05:29:56 +08:00
|
|
|
//===-- CompletionRequestTest.cpp -------------------------------*- C++ -*-===//
|
|
|
|
|
//
|
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
|
//
|
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
|
//
|
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
|
|
#include "gtest/gtest.h"
|
|
|
|
|
|
|
|
|
|
#include "lldb/Utility/CompletionRequest.h"
|
|
|
|
|
using namespace lldb_private;
|
|
|
|
|
|
|
|
|
|
TEST(CompletionRequest, Constructor) {
|
2018-07-14 02:28:14 +08:00
|
|
|
std::string command = "a bad c";
|
|
|
|
|
const unsigned cursor_pos = 3;
|
Refactoring for for the internal command line completion API (NFC)
Summary:
This patch refactors the internal completion API. It now takes (as far as possible) a single
CompletionRequest object instead o half a dozen in/out/in-out parameters. The CompletionRequest
contains a common superset of the different parameters as far as it makes sense. This includes
the raw command line string and raw cursor position, which should make the `expr` command
possible to implement (at least without hacks that reconstruct the command line from the args).
This patch is not intended to change the observable behavior of lldb in any way. It's also as
minimal as possible and doesn't attempt to fix all the problems the API has.
Some Q&A:
Q: Why is this not fixing all the problems in the completion API?
A: Because is a blocker for the expr command completion which I want to get in ASAP. This is the
smallest patch that unblocks the expr completion patch and which allows trivial refactoring in the future.
The patch also doesn't really change the internal information flow in the API, so that hopefully
saves us from ever having to revert and resubmit this humongous patch.
Q: Can we merge all the copy-pasted code in the completion methods
(like computing the current incomplete arg) into CompletionRequest class?
A: Yes, but it's out of scope for this patch.
Q: Why the `word_complete = request.GetWordComplete(); ... ` pattern?
A: I don't want to add a getter that returns a reference to the internal integer. So we have
to use a temporary variable and the Getter/Setter instead. We don't throw exceptions
from what I can tell, so the behavior doesn't change.
Q: Why are we not owning the list of matches?
A: Because that's how the previous API works. But that should be fixed too (in another patch).
Q: Can we make the constructor simpler and compute some of the values from the plain command?
A: I think this works, but I rather want to have this in a follow up commit. Especially when making nested
request it's a bit awkward that the parsed arguments behave as both input/output (as we should in theory
propagate the changes on the nested request back to the parent request if we don't want to change the
behavior too much).
Q: Can't we pass one const request object and then just return another result object instead of mixing
them together in one in/out parameter?
A: It's hard to get keep the same behavior with that pattern, but I think we can also get a nice API with just
a single request object. If we make all input parameters read-only, we have a clear separation between what
is actually an input and what an output parameter (and hopefully we get rid of the in-out parameters).
Q: Can we throw out the 'match' variables that are not implemented according to the comment?
A: We currently just forward them as in the old code to the different methods, even though I think
they are really not used. We can easily remove and readd them once every single completion method just
takes a CompletionRequest, but for now I prefer NFC behavior from the perspective of the API user.
Reviewers: davide, jingham, labath
Reviewed By: jingham
Subscribers: mgorny, friss, lldb-commits
Differential Revision: https://reviews.llvm.org/D48796
llvm-svn: 336146
2018-07-03 05:29:56 +08:00
|
|
|
const int arg_index = 1;
|
2018-07-14 02:28:14 +08:00
|
|
|
const int arg_cursor_pos = 1;
|
Refactoring for for the internal command line completion API (NFC)
Summary:
This patch refactors the internal completion API. It now takes (as far as possible) a single
CompletionRequest object instead o half a dozen in/out/in-out parameters. The CompletionRequest
contains a common superset of the different parameters as far as it makes sense. This includes
the raw command line string and raw cursor position, which should make the `expr` command
possible to implement (at least without hacks that reconstruct the command line from the args).
This patch is not intended to change the observable behavior of lldb in any way. It's also as
minimal as possible and doesn't attempt to fix all the problems the API has.
Some Q&A:
Q: Why is this not fixing all the problems in the completion API?
A: Because is a blocker for the expr command completion which I want to get in ASAP. This is the
smallest patch that unblocks the expr completion patch and which allows trivial refactoring in the future.
The patch also doesn't really change the internal information flow in the API, so that hopefully
saves us from ever having to revert and resubmit this humongous patch.
Q: Can we merge all the copy-pasted code in the completion methods
(like computing the current incomplete arg) into CompletionRequest class?
A: Yes, but it's out of scope for this patch.
Q: Why the `word_complete = request.GetWordComplete(); ... ` pattern?
A: I don't want to add a getter that returns a reference to the internal integer. So we have
to use a temporary variable and the Getter/Setter instead. We don't throw exceptions
from what I can tell, so the behavior doesn't change.
Q: Why are we not owning the list of matches?
A: Because that's how the previous API works. But that should be fixed too (in another patch).
Q: Can we make the constructor simpler and compute some of the values from the plain command?
A: I think this works, but I rather want to have this in a follow up commit. Especially when making nested
request it's a bit awkward that the parsed arguments behave as both input/output (as we should in theory
propagate the changes on the nested request back to the parent request if we don't want to change the
behavior too much).
Q: Can't we pass one const request object and then just return another result object instead of mixing
them together in one in/out parameter?
A: It's hard to get keep the same behavior with that pattern, but I think we can also get a nice API with just
a single request object. If we make all input parameters read-only, we have a clear separation between what
is actually an input and what an output parameter (and hopefully we get rid of the in-out parameters).
Q: Can we throw out the 'match' variables that are not implemented according to the comment?
A: We currently just forward them as in the old code to the different methods, even though I think
they are really not used. We can easily remove and readd them once every single completion method just
takes a CompletionRequest, but for now I prefer NFC behavior from the perspective of the API user.
Reviewers: davide, jingham, labath
Reviewed By: jingham
Subscribers: mgorny, friss, lldb-commits
Differential Revision: https://reviews.llvm.org/D48796
llvm-svn: 336146
2018-07-03 05:29:56 +08:00
|
|
|
const int match_start = 2345;
|
|
|
|
|
const int match_max_return = 12345;
|
|
|
|
|
StringList matches;
|
2018-09-14 05:26:00 +08:00
|
|
|
CompletionResult result;
|
2018-07-14 02:28:14 +08:00
|
|
|
|
|
|
|
|
CompletionRequest request(command, cursor_pos, match_start, match_max_return,
|
2018-09-14 05:26:00 +08:00
|
|
|
result);
|
|
|
|
|
result.GetMatches(matches);
|
Refactoring for for the internal command line completion API (NFC)
Summary:
This patch refactors the internal completion API. It now takes (as far as possible) a single
CompletionRequest object instead o half a dozen in/out/in-out parameters. The CompletionRequest
contains a common superset of the different parameters as far as it makes sense. This includes
the raw command line string and raw cursor position, which should make the `expr` command
possible to implement (at least without hacks that reconstruct the command line from the args).
This patch is not intended to change the observable behavior of lldb in any way. It's also as
minimal as possible and doesn't attempt to fix all the problems the API has.
Some Q&A:
Q: Why is this not fixing all the problems in the completion API?
A: Because is a blocker for the expr command completion which I want to get in ASAP. This is the
smallest patch that unblocks the expr completion patch and which allows trivial refactoring in the future.
The patch also doesn't really change the internal information flow in the API, so that hopefully
saves us from ever having to revert and resubmit this humongous patch.
Q: Can we merge all the copy-pasted code in the completion methods
(like computing the current incomplete arg) into CompletionRequest class?
A: Yes, but it's out of scope for this patch.
Q: Why the `word_complete = request.GetWordComplete(); ... ` pattern?
A: I don't want to add a getter that returns a reference to the internal integer. So we have
to use a temporary variable and the Getter/Setter instead. We don't throw exceptions
from what I can tell, so the behavior doesn't change.
Q: Why are we not owning the list of matches?
A: Because that's how the previous API works. But that should be fixed too (in another patch).
Q: Can we make the constructor simpler and compute some of the values from the plain command?
A: I think this works, but I rather want to have this in a follow up commit. Especially when making nested
request it's a bit awkward that the parsed arguments behave as both input/output (as we should in theory
propagate the changes on the nested request back to the parent request if we don't want to change the
behavior too much).
Q: Can't we pass one const request object and then just return another result object instead of mixing
them together in one in/out parameter?
A: It's hard to get keep the same behavior with that pattern, but I think we can also get a nice API with just
a single request object. If we make all input parameters read-only, we have a clear separation between what
is actually an input and what an output parameter (and hopefully we get rid of the in-out parameters).
Q: Can we throw out the 'match' variables that are not implemented according to the comment?
A: We currently just forward them as in the old code to the different methods, even though I think
they are really not used. We can easily remove and readd them once every single completion method just
takes a CompletionRequest, but for now I prefer NFC behavior from the perspective of the API user.
Reviewers: davide, jingham, labath
Reviewed By: jingham
Subscribers: mgorny, friss, lldb-commits
Differential Revision: https://reviews.llvm.org/D48796
llvm-svn: 336146
2018-07-03 05:29:56 +08:00
|
|
|
|
|
|
|
|
EXPECT_STREQ(request.GetRawLine().str().c_str(), command.c_str());
|
|
|
|
|
EXPECT_EQ(request.GetRawCursorPos(), cursor_pos);
|
|
|
|
|
EXPECT_EQ(request.GetCursorIndex(), arg_index);
|
|
|
|
|
EXPECT_EQ(request.GetCursorCharPosition(), arg_cursor_pos);
|
|
|
|
|
EXPECT_EQ(request.GetMatchStartPoint(), match_start);
|
|
|
|
|
EXPECT_EQ(request.GetMaxReturnElements(), match_max_return);
|
2018-07-14 02:28:14 +08:00
|
|
|
EXPECT_EQ(request.GetWordComplete(), false);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(request.GetPartialParsedLine().GetArgumentCount(), 2u);
|
|
|
|
|
EXPECT_STREQ(request.GetPartialParsedLine().GetArgumentAtIndex(1), "b");
|
2018-07-28 02:42:46 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
TEST(CompletionRequest, DuplicateFiltering) {
|
|
|
|
|
std::string command = "a bad c";
|
|
|
|
|
const unsigned cursor_pos = 3;
|
|
|
|
|
StringList matches;
|
|
|
|
|
|
2018-09-14 05:26:00 +08:00
|
|
|
CompletionResult result;
|
|
|
|
|
CompletionRequest request(command, cursor_pos, 0, 0, result);
|
|
|
|
|
result.GetMatches(matches);
|
2018-07-28 02:42:46 +08:00
|
|
|
|
|
|
|
|
EXPECT_EQ(0U, request.GetNumberOfMatches());
|
|
|
|
|
|
|
|
|
|
// Add foo twice
|
|
|
|
|
request.AddCompletion("foo");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(1U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(1U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
|
|
|
|
|
request.AddCompletion("foo");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(1U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(1U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
|
|
|
|
|
// Add bar twice
|
|
|
|
|
request.AddCompletion("bar");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(2U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(2U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
|
|
|
|
|
request.AddCompletion("bar");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(2U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(2U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
|
|
|
|
|
// Add foo again.
|
|
|
|
|
request.AddCompletion("foo");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(2U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(2U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
|
|
|
|
|
// Add something with an existing prefix
|
|
|
|
|
request.AddCompletion("foobar");
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(3U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(3U, matches.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
EXPECT_STREQ("foobar", matches.GetStringAtIndex(2));
|
|
|
|
|
}
|
|
|
|
|
|
2018-09-14 05:26:00 +08:00
|
|
|
TEST(CompletionRequest, DuplicateFilteringWithComments) {
|
|
|
|
|
std::string command = "a bad c";
|
|
|
|
|
const unsigned cursor_pos = 3;
|
|
|
|
|
StringList matches, descriptions;
|
|
|
|
|
|
|
|
|
|
CompletionResult result;
|
|
|
|
|
CompletionRequest request(command, cursor_pos, 0, 0, result);
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(0U, request.GetNumberOfMatches());
|
|
|
|
|
|
|
|
|
|
// Add foo twice with same comment
|
|
|
|
|
request.AddCompletion("foo", "comment");
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(1U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(1U, matches.GetSize());
|
|
|
|
|
EXPECT_EQ(1U, descriptions.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(0));
|
|
|
|
|
|
|
|
|
|
request.AddCompletion("foo", "comment");
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(1U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(1U, matches.GetSize());
|
|
|
|
|
EXPECT_EQ(1U, descriptions.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(0));
|
|
|
|
|
|
|
|
|
|
// Add bar twice with different comments
|
|
|
|
|
request.AddCompletion("bar", "comment");
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(2U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(2U, matches.GetSize());
|
|
|
|
|
EXPECT_EQ(2U, descriptions.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
|
|
|
|
|
request.AddCompletion("bar", "another comment");
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(3U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(3U, matches.GetSize());
|
|
|
|
|
EXPECT_EQ(3U, descriptions.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(1));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(2));
|
|
|
|
|
EXPECT_STREQ("another comment", descriptions.GetStringAtIndex(2));
|
|
|
|
|
|
|
|
|
|
// Add foo again with no comment
|
|
|
|
|
request.AddCompletion("foo");
|
|
|
|
|
result.GetMatches(matches);
|
|
|
|
|
result.GetDescriptions(descriptions);
|
|
|
|
|
|
|
|
|
|
EXPECT_EQ(4U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_EQ(4U, matches.GetSize());
|
|
|
|
|
EXPECT_EQ(4U, descriptions.GetSize());
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(0));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(1));
|
|
|
|
|
EXPECT_STREQ("comment", descriptions.GetStringAtIndex(1));
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(2));
|
|
|
|
|
EXPECT_STREQ("another comment", descriptions.GetStringAtIndex(2));
|
|
|
|
|
EXPECT_STREQ("foo", matches.GetStringAtIndex(3));
|
|
|
|
|
EXPECT_STREQ("", descriptions.GetStringAtIndex(3));
|
|
|
|
|
}
|
|
|
|
|
|
2018-07-28 02:42:46 +08:00
|
|
|
TEST(CompletionRequest, TestCompletionOwnership) {
|
|
|
|
|
std::string command = "a bad c";
|
|
|
|
|
const unsigned cursor_pos = 3;
|
|
|
|
|
StringList matches;
|
|
|
|
|
|
2018-09-14 05:26:00 +08:00
|
|
|
CompletionResult result;
|
|
|
|
|
CompletionRequest request(command, cursor_pos, 0, 0, result);
|
2018-07-28 02:42:46 +08:00
|
|
|
|
|
|
|
|
std::string Temporary = "bar";
|
|
|
|
|
request.AddCompletion(Temporary);
|
|
|
|
|
// Manipulate our completion. The request should have taken a copy, so that
|
|
|
|
|
// shouldn't influence anything.
|
|
|
|
|
Temporary[0] = 'f';
|
2018-07-14 02:28:14 +08:00
|
|
|
|
2018-09-14 05:26:00 +08:00
|
|
|
result.GetMatches(matches);
|
2018-07-28 02:42:46 +08:00
|
|
|
EXPECT_EQ(1U, request.GetNumberOfMatches());
|
|
|
|
|
EXPECT_STREQ("bar", matches.GetStringAtIndex(0));
|
Refactoring for for the internal command line completion API (NFC)
Summary:
This patch refactors the internal completion API. It now takes (as far as possible) a single
CompletionRequest object instead o half a dozen in/out/in-out parameters. The CompletionRequest
contains a common superset of the different parameters as far as it makes sense. This includes
the raw command line string and raw cursor position, which should make the `expr` command
possible to implement (at least without hacks that reconstruct the command line from the args).
This patch is not intended to change the observable behavior of lldb in any way. It's also as
minimal as possible and doesn't attempt to fix all the problems the API has.
Some Q&A:
Q: Why is this not fixing all the problems in the completion API?
A: Because is a blocker for the expr command completion which I want to get in ASAP. This is the
smallest patch that unblocks the expr completion patch and which allows trivial refactoring in the future.
The patch also doesn't really change the internal information flow in the API, so that hopefully
saves us from ever having to revert and resubmit this humongous patch.
Q: Can we merge all the copy-pasted code in the completion methods
(like computing the current incomplete arg) into CompletionRequest class?
A: Yes, but it's out of scope for this patch.
Q: Why the `word_complete = request.GetWordComplete(); ... ` pattern?
A: I don't want to add a getter that returns a reference to the internal integer. So we have
to use a temporary variable and the Getter/Setter instead. We don't throw exceptions
from what I can tell, so the behavior doesn't change.
Q: Why are we not owning the list of matches?
A: Because that's how the previous API works. But that should be fixed too (in another patch).
Q: Can we make the constructor simpler and compute some of the values from the plain command?
A: I think this works, but I rather want to have this in a follow up commit. Especially when making nested
request it's a bit awkward that the parsed arguments behave as both input/output (as we should in theory
propagate the changes on the nested request back to the parent request if we don't want to change the
behavior too much).
Q: Can't we pass one const request object and then just return another result object instead of mixing
them together in one in/out parameter?
A: It's hard to get keep the same behavior with that pattern, but I think we can also get a nice API with just
a single request object. If we make all input parameters read-only, we have a clear separation between what
is actually an input and what an output parameter (and hopefully we get rid of the in-out parameters).
Q: Can we throw out the 'match' variables that are not implemented according to the comment?
A: We currently just forward them as in the old code to the different methods, even though I think
they are really not used. We can easily remove and readd them once every single completion method just
takes a CompletionRequest, but for now I prefer NFC behavior from the perspective of the API user.
Reviewers: davide, jingham, labath
Reviewed By: jingham
Subscribers: mgorny, friss, lldb-commits
Differential Revision: https://reviews.llvm.org/D48796
llvm-svn: 336146
2018-07-03 05:29:56 +08:00
|
|
|
}
|