public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Julian Lenz <j.j.lenz@swansea.ac.uk>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Reason for missing notes for incomplete-type errors in standard headers
Date: Fri, 5 Aug 2022 17:55:39 +0100	[thread overview]
Message-ID: <CAH6eHdTs2HcjVTkha6irihRCoRvxAS6RtZu+g4_8h8AFojcuTw@mail.gmail.com> (raw)
In-Reply-To: <a8303dbd-a5ba-6497-c336-552bfe23950d@swansea.ac.uk>

On Fri, 5 Aug 2022 at 17:39, Julian Lenz via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi everybody,
>
> TL;DR:
>
> What is the reason that `error: '<some class>' has incomplete type` does
> not give a note about where the forward declaration happened for
> standard library classes?

Probably because the declaration happens in a system header.

Does -Wsystem-headers change it?

  reply	other threads:[~2022-08-05 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 16:38 Julian Lenz
2022-08-05 16:55 ` Jonathan Wakely [this message]
2022-08-05 20:27   ` Julian Lenz

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=CAH6eHdTs2HcjVTkha6irihRCoRvxAS6RtZu+g4_8h8AFojcuTw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=j.j.lenz@swansea.ac.uk \
    /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).