From: Bruno Haible <bruno@clisp.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: static_assert in G++
Date: Thu, 10 Jan 2019 21:57:27 +0100 [thread overview]
Message-ID: <3471414.FuaTGlBU7V@omega> (raw)
In-Reply-To: <CAOnWdogaevZwMD=2Db=m3n_F78NgJCbFUNr2rdF31UbXwMOs7w@mail.gmail.com>
Reuben Thomas wrote:
> Would it be good to say something about "by default", so that future
> readers aren't confused as I was?
Comments are good. But we can't put all possible thoughts and considerations
into comments. Readers can look up the mailing list discussion, based on the
date of the commit.
OTOH, you are always free to adjust comments, when you feel that it's worth it.
Bruno
prev parent reply other threads:[~2019-01-10 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 12:17 static_assert in G++ Reuben Thomas
2019-01-10 20:08 ` Bruno Haible
2019-01-10 20:21 ` Reuben Thomas
2019-01-10 20:57 ` Bruno Haible [this message]
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3471414.FuaTGlBU7V@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.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).