public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Arthur Cohen <cohenarthur@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5559] gccrs: const generics: Make sure const generic types are visited properly Date: Tue, 31 Jan 2023 13:16:24 +0000 (GMT) [thread overview] Message-ID: <20230131131624.3114D385B512@sourceware.org> (raw) https://gcc.gnu.org/g:288b6298a6ae9356122362cd604e3582d8decd26 commit r13-5559-g288b6298a6ae9356122362cd604e3582d8decd26 Author: Arthur Cohen <arthur.cohen@embecosm.com> Date: Mon Sep 12 15:53:01 2022 +0200 gccrs: const generics: Make sure const generic types are visited properly ...in all contexts. gcc/testsuite/ChangeLog: * rust/compile/const_generics_7.rs: New test. Diff: --- gcc/testsuite/rust/compile/const_generics_7.rs | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/gcc/testsuite/rust/compile/const_generics_7.rs b/gcc/testsuite/rust/compile/const_generics_7.rs new file mode 100644 index 00000000000..2c128db92ea --- /dev/null +++ b/gcc/testsuite/rust/compile/const_generics_7.rs @@ -0,0 +1,17 @@ +struct S<const N: usize>; + +pub fn foo<const N: FooBar>() {} // { dg-error "failed to resolve" } +type Foo<const N: FooBar> = S<N>; // { dg-error "failed to resolve" } +struct Foo2<const N: FooBar>; // { dg-error "failed to resolve" } +enum Foo3<const N: FooBar> { // { dg-error "failed to resolve" } + Foo, + Bar, +} +union Foo4<const N: FooBar> { // { dg-error "failed to resolve" } + a: usize, + b: i32, +} +trait Fooable<const N: FooBar> {} // { dg-error "failed to resolve" } + +trait Traitable {} +impl<const N: FooBar> Traitable for Foo2<N> {} // { dg-error "failed to resolve" }
reply other threads:[~2023-01-31 13:16 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=20230131131624.3114D385B512@sourceware.org \ --to=cohenarthur@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).