public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: gcc@gcc.gnu.org
Subject: Local type inference with auto is in C2X
Date: Thu, 03 Nov 2022 11:37:35 +0100	[thread overview]
Message-ID: <87zgd8fhn4.fsf@oldenburg.str.redhat.com> (raw)

So apparently auto was voted in to the committee draft of C2X at the
last minute.  I wonder how this aligns with the WG14 charter, given the
lack of implementation experience with this feature, but it looks like
we are now stuck with it.

My main worry is that both Clang and GCC still enable implicit ints by
default.  This means that auto variables have type int always, and that
can subtly alter the meaning of programs.  The only indication that this
has happened in a code base is a warning that went away (!).  I don't
like that.

My original plan was to port upstreams & distributions away from
implicit ints (again, configure scripts are problematic), and then have
at least one GCC release that disables implicit ints in the default
language mode.  But I'm not sure if that's now possible: the porting
will not have propagated widely once GCC 13 releases, so rejecting
implicit ints in GCC 13 might be too early.  GCC 14 might want to switch
to C23/C24 mode by default, activating auto support, if the standard
comes out in 2023 (which apparently is the plan).  Then we would go from
warning to changed semantics in a single release.

Comments?

Thanks,
Florian


             reply	other threads:[~2022-11-03 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 10:37 Florian Weimer [this message]
2022-11-03 15:19 ` Michael Matz
2022-11-04 14:16   ` David Brown
2022-11-03 18:04 ` Joseph Myers
2022-11-03 18:33   ` Florian Weimer

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=87zgd8fhn4.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gcc@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).