diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2017-09-21 22:32:28 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2017-09-21 22:32:28 +0200 |
| commit | 1ce0963557a8bbd61ca27cc448f459ba8ceaee56 (patch) | |
| tree | fff3f32a9e73e9d9f98b1fabe4af7109b224f827 | |
| parent | e57c75e00a0fbccb47254a844bbfe5d7a9e0ee06 (diff) | |
Fix typo
| -rw-r--r-- | doc/manual.cli | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 914123d..5d6ef08 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -1748,8 +1748,8 @@ implementation re-uses the comparison operators provided by \c{std::vector} There is palpable difference between the two cases: the first merely uses \c{std.core} interface while the second is \i{based on} and, in a sense, \i{extends} it which feels like a stronger relationship. Re-exporting -\c{std.core} (or, better yet, \c{std.core.version}, should it become -available) does not seem unreasonable. +\c{std.core} (or, better yet, \c{std.core.vector}, should it become available) +does not seem unreasonable. Note also that there is no re-export of headers nor header inclusion visibility in the implementation units. Specifically, in the previous example, |