From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Gabriel Dos Reis <gdr@axiomatics.org>
Cc: Andrew Sutton <andrew.n.sutton@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [c++-concepts]: constraint association
Date: Sat, 22 Jun 2013 17:24:00 -0000 [thread overview]
Message-ID: <CAAiZkiDROXQ3Rv0ueAAaSprk7u93hzJ3fvaVWZgdwr-qt_b_Nw@mail.gmail.com> (raw)
In-Reply-To: <87ppvejcj7.fsf@euclid.axiomatics.org>
On Sat, Jun 22, 2013 at 12:11 PM, Gabriel Dos Reis <gdr@axiomatics.org> wrote:
> Andrew Sutton <andrew.n.sutton@gmail.com> writes:
>
> | I the long term, I think we'll end up having constraints attached to
> | declarations wherever we constrain auto (PARM_DECL, VAR_DECL, etc).
> | Although now that I'm looking, it seems that lang_decl_parm does not
> | inherit lang_min. Hmm...
> |
> | Mostly, though, I'm not sure where I could put it where both
> | TEMPLATE_DECL and FUNCTION_DECL would have constraints.
>
> I think we want constraints for:
>
> * FUNCTION_DECL
> * TEMPLATE_DECL
> * TYPE_DECL
> * TEMPLATE_PARM_DECL
Well, thinking more about it, I believe we want it only for
* TEMPLATE_DECL
* TEMPLATE_PARM_DECL.
The FUNCTION_DECL and the TYPE_DECL gets their constraints
from the abstract instantiation of the associated TEMPLATE_DECL.
The comment for PARM_DECL extends to VAR_DECL -- only temploids
get constraints and non-temploid vars declared 'auto' at the source
level have types
that are TEMPLATE_TYPE_PARM, hence should get their constraints properly set.
-- Gaby
next prev parent reply other threads:[~2013-06-22 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 15:57 Andrew Sutton
2013-06-22 16:41 ` Gabriel Dos Reis
2013-06-22 16:56 ` Andrew Sutton
2013-06-22 17:11 ` Gabriel Dos Reis
2013-06-22 17:24 ` Gabriel Dos Reis [this message]
2013-06-22 18:05 ` Andrew Sutton
2013-06-22 18:27 ` Gabriel Dos Reis
2013-06-22 20:11 ` Andrew Sutton
2013-06-22 22:03 ` Gabriel Dos Reis
2013-06-22 22:55 ` Andrew Sutton
2013-06-22 23:27 ` Gabriel Dos Reis
2013-06-22 22:56 ` Gabriel Dos Reis
2013-06-22 23:04 ` Andrew Sutton
2013-06-22 23:43 ` Gabriel Dos Reis
2013-06-24 15:57 ` Andrew Sutton
2013-06-24 17:16 ` Gabriel Dos Reis
2013-06-27 14:38 ` Jason Merrill
2013-06-27 14:47 ` Jason Merrill
2014-06-28 14:57 [c++-concepts] " Andrew Sutton
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=CAAiZkiDROXQ3Rv0ueAAaSprk7u93hzJ3fvaVWZgdwr-qt_b_Nw@mail.gmail.com \
--to=gdr@integrable-solutions.net \
--cc=andrew.n.sutton@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@axiomatics.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).