[committed] libstdc++: Fix typo in comment in hashtable.h
François Dumont
frs.dumont@gmail.com
Thu Nov 7 17:50:20 GMT 2024
On 07/11/2024 16:48, Jonathan Wakely wrote:
> And tweak grammar in a couple of comments.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/hashtable.h: Fix spelling in comment.
> ---
> Pushed as obvious.
>
> libstdc++-v3/include/bits/hashtable.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libstdc++-v3/include/bits/hashtable.h b/libstdc++-v3/include/bits/hashtable.h
> index 47321a9cb13..8b312d25d7a 100644
> --- a/libstdc++-v3/include/bits/hashtable.h
> +++ b/libstdc++-v3/include/bits/hashtable.h
> @@ -344,7 +344,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> struct __hash_code_base_access : __hash_code_base
> { using __hash_code_base::_M_bucket_index; };
>
> - // To get bucket index we need _RangeHash not to throw.
> + // To get bucket index we need _RangeHash to be non-throwing.
> static_assert(is_nothrow_default_constructible<_RangeHash>::value,
> "Functor used to map hash code to bucket index"
> " must be nothrow default constructible");
> @@ -353,7 +353,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> "Functor used to map hash code to bucket index must be"
> " noexcept");
>
> - // To compute bucket index we also need _ExtratKey not to throw.
> + // To compute bucket index we also need _ExtractKey be non-throwing.
Shouldn't it be:
// To compute bucket index we also need _ExtractKey *to* be non-throwing.
?
More information about the Libstdc++
mailing list