forked from boostorg/container
Merge branch 'container-misc-typos' of https://github.com/luzpaz/container into luzpaz-container-misc-typos
This commit is contained in:
commit
3a2f61fdb0
10 files changed
+16
-15
No files matched your search
+3
-2
@@ -366,8 +366,8 @@ operations provide stronger exception safety guarantees than in vector:
|
||||
[[erase] [no-throw unless copy/move construction/assignment of `T` throw (basic)] [no-throw]]
|
||||
]
|
||||
|
||||
[*Memory overhead]. The C++ standard does not specifiy requirements on memory consumption, but virtually any implementation
|
||||
of `vector` has the same behavior wih respect to memory usage: the memory allocated by a `vector` v with n elements of type T
|
||||
[*Memory overhead]. The C++ standard does not specify requirements on memory consumption, but virtually any implementation
|
||||
of `vector` has the same behavior with respect to memory usage: the memory allocated by a `vector` v with n elements of type T
|
||||
is
|
||||
|
||||
m[sub v] = c\u2219e,
|
||||
@@ -1254,6 +1254,7 @@ use [*Boost.Container]? There are several reasons for that:
|
||||
* Fixed bugs:
|
||||
* [@https://github.com/boostorg/container/issues/82 GitHub #82: ['"Function definition in header file"]].
|
||||
* [@https://github.com/boostorg/container/issues/83 GitHub #83: ['"Iterator zero incrementing leads to assert on empty vector"]].
|
||||
* [@https://github.com/boostorg/container/pull/85 GitHub #85: ['"container: misc-typos"]].
|
||||
* [@https://github.com/boostorg/container/pull/86 GitHub #86: ['"Add missing warning re-enabling include"]].
|
||||
|
||||
[endsect]
|
||||
|
||||
Reference in new issue
Block a user