From f67e91d295772171c4d554469f6434ed9a546c25 Mon Sep 17 00:00:00 2001 From: Amir Livneh Date: Sat, 9 Mar 2019 19:15:27 -0500 Subject: [PATCH] Use `memoizes` instead of `mnemonizes` in the context of caching (#1383) * Use `memoizes` instead of `mnemonizes` in the context of caching While apparently, 'mnemonizes' is a word, I don't think it's the best choice here. * Update isocpp.dic --- CppCoreGuidelines.md | 2 +- scripts/hunspell/isocpp.dic | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index e96e661..c11ce96 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -16256,7 +16256,7 @@ e.g. because it is in a library that you cannot modify. A `const` member function can modify the value of an object that is `mutable` or accessed through a pointer member. A common use is to maintain a cache rather than repeatedly do a complicated computation. -For example, here is a `Date` that caches (mnemonizes) its string representation to simplify repeated uses: +For example, here is a `Date` that caches (memoizes) its string representation to simplify repeated uses: class Date { public: diff --git a/scripts/hunspell/isocpp.dic b/scripts/hunspell/isocpp.dic index 0497316..a333866 100644 --- a/scripts/hunspell/isocpp.dic +++ b/scripts/hunspell/isocpp.dic @@ -304,6 +304,7 @@ memcmp memmove memoization memoized +memoizes memset metameta metaprogram