public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-6625] libstdc++: Fix typo in comment
Date: Mon, 13 Mar 2023 10:34:58 +0000 (GMT)	[thread overview]
Message-ID: <20230313103458.19E1E3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:a1d4d92d6a306e4142949e16e0cac075519256c7

commit r13-6625-ga1d4d92d6a306e4142949e16e0cac075519256c7
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 13 10:30:12 2023 +0000

    libstdc++: Fix typo in comment
    
    Reported by Jonny Grant.
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/allocator.h: Fix typo in comment.

Diff:
---
 libstdc++-v3/include/bits/allocator.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/bits/allocator.h b/libstdc++-v3/include/bits/allocator.h
index be67789c1cd..abbd753d33d 100644
--- a/libstdc++-v3/include/bits/allocator.h
+++ b/libstdc++-v3/include/bits/allocator.h
@@ -62,7 +62,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 
   // Since C++20 the primary template should be used for allocator<void>,
   // but then it would have a non-trivial default ctor and dtor for C++20,
-  // but trivial for C++98-17, which would be an ABI incompatibiliy between
+  // but trivial for C++98-17, which would be an ABI incompatibility between
   // different standard dialects. So C++20 still uses the allocator<void>
   // explicit specialization, with the historical ABI properties, but with
   // the same members that are present in the primary template.

                 reply	other threads:[~2023-03-13 10:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230313103458.19E1E3858D32@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).