Following D151810, this changes GetChildAtNamePath to take a path of StringRef
values instead of ConstString.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lgtm
lldb/include/lldb/Core/ValueObject.h | ||
---|---|---|
483 | Guessing removing the parameter is fine because no callers were actually passing it? |
lldb/source/Core/ValueObject.cpp | ||
---|---|---|
434 | I don’t think this qualifies for ‘auto’ according to the LLVM coding guidelines. |
lldb/include/lldb/Core/ValueObject.h | ||
---|---|---|
483 | I forgot I had made this change too. Correct, no callers were using this, so I removed it. I can imagine there could be a hypothetical case that uses it to determine a fallback action, but none do and it seems unlikely. | |
lldb/source/Core/ValueObject.cpp | ||
434 | I find the guidelines to be not specific enough. Case in point, this section shows auto being used in range for loops: https://llvm.org/docs/CodingStandards.html#beware-unnecessary-copies-with-auto |
lldb/source/Core/ValueObject.cpp | ||
---|---|---|
434 | nit: mark name as const -> const auto name. |
lldb/source/Core/ValueObject.cpp | ||
---|---|---|
434 | yes I figure a StringRef is cheap to copy. |
Guessing removing the parameter is fine because no callers were actually passing it?