StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #64 from mpark/T80

Browse Source 
T.80: Fixed minor typos and a missing template argument in an example.
This commit is contained in:
Gabriel Dos Reis 2015-09-22 03:04:29 -07:00
commit 4b480fa0fc
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CppCoreGuidelines.md
View File

@ -9762,7 +9762,7 @@ The two language mechanisms can be use effectively in combination, but a few des
};
template<typename T>
class Vector : public Container {
class Vector : public Container<T> {
public:
// ...
};
@ -9773,12 +9773,12 @@ The two language mechanisms can be use effectively in combination, but a few des
It is probably a dumb idea to define a `sort` as a member function of a container,
but it is not unheard of and it makes a good example of what not to do.
Given this, the compiler cannot know if `vector<int>::sort()` is called, so it must generate code for it.
Similar for `vector<string>::sort()`.
Given this, the compiler cannot know if `Vector<int>::sort()` is called, so it must generate code for it.
Similar for `Vector<string>::sort()`.
Unless those two functions are called that's code bloat.
Imagine what this would do to a class hierarchy with dozens of member functions and dozens of derived classes with many instantiations.
**Note**: In many cases you can provide a stable interface by not parameterize a base; see [???](#Rt-abi).
**Note**: In many cases you can provide a stable interface by not parameterizing a base; see [???](#Rt-abi).
**Enforcement**: