diff options
| author | Sean Silva <silvas@purdue.edu> | 2013-03-22 23:52:38 +0000 |
|---|---|---|
| committer | Sean Silva <silvas@purdue.edu> | 2013-03-22 23:52:38 +0000 |
| commit | 928ef439a5ab104d706b64f9da28eda32398bbf3 (patch) | |
| tree | be1785bb07a6f8038e70939647822731adf115e8 | |
| parent | 0059eb1e2e779f6537c1da9d9ff4679e19e23628 (diff) | |
[docs] Slight reword for precision.
The new wording cannot be construed as suggesting the use of
SmallVectorImpl<T> as e.g. a class member (just because the class
happens to be in an interface).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177778 91177308-0d34-0410-b5e6-96231b3b80d8
| -rw-r--r-- | docs/ProgrammersManual.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ProgrammersManual.rst b/docs/ProgrammersManual.rst index eed12e94be..87b802001c 100644 --- a/docs/ProgrammersManual.rst +++ b/docs/ProgrammersManual.rst @@ -628,7 +628,7 @@ SmallVector also provides a nice portable and efficient replacement for .. note:: - Prefer to use ``SmallVectorImpl<T>`` in interfaces. + Prefer to use ``SmallVectorImpl<T>`` as a parameter type. In APIs that don't care about the "small size" (most?), prefer to use the ``SmallVectorImpl<T>`` class, which is basically just the "vector |