From: Ryan Nicholl <r.p.nicholl@gmail.com>
To: overseers@gcc.gnu.org
Subject: Account request
Date: Tue, 02 Dec 2014 17:17:00 -0000 [thread overview]
Message-ID: <CAPuLQKyzvKi9nDF256XnVzve1JsePkw_-sbvNvsjusJFVUUZTg@mail.gmail.com> (raw)
I am looking to create an account on the GCC bug-tracker in order to
submit some feature requests.
I get this message:
User account creation has been restricted.
________________________________
Contact your administrator or the maintainer (overseers@gcc.gnu.org)
for information about creating an account.
Since I only have a couple suggestions, it may be more convenient for
you to add them yourself rather than add me an account.
I would like to suggest -Wident=foo which shall warn whenever foo is
encountered in the code (useful for functions like gets which are
specific to your codebase.
Next is -Wextra-copy, which is a C++ specific option, to warn when
calling a function with a value that the compiler can tell will be
destroyed soon, without casting it to an r-value reference.
Another possible suggestion is -felide-copies, which does violate the
C++ standard, but would take the warnings above, and simply convert
them to rvalue reference calls.
Thank you for your time.
--
Thank you,
Ryan P. Nicholl
Freelance C++ Developer
(678)358-7765
r.p.nicholl@gmail.com
reply other threads:[~2014-11-30 19:28 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=CAPuLQKyzvKi9nDF256XnVzve1JsePkw_-sbvNvsjusJFVUUZTg@mail.gmail.com \
--to=r.p.nicholl@gmail.com \
--cc=overseers@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).