Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [FYI] Allow empty struct expressions in Rust
Date: Thu, 21 Jul 2016 21:14:00 -0000	[thread overview]
Message-ID: <87lh0ulmmh.fsf@tromey.com> (raw)
In-Reply-To: <1468271438-5389-1-git-send-email-tom@tromey.com> (Tom Tromey's	message of "Mon, 11 Jul 2016 15:10:38 -0600")

>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:

Tom> I learned recently that empty struct expressions, like "X{}", have been
Tom> promoted from experimental to stable in Rust.  This patch changes the
Tom> Rust expression parser to allow this case.

Tom> New test case included.
Tom> Built and regtested on x86-64 Fedora 23, using Rust 1.11 beta.

Tom> I plan to check this in after a reasonable interval.

Tom> 2016-07-11  Tom Tromey  <tom@tromey.com>

Tom> 	* rust-lang.c (rust_tuple_struct_type_p): Return false for empty
Tom> 	structs.
Tom> 	* rust-exp.y (struct_expr_list): Allow empty elements.

I'm checking this in now.

Tom


      parent reply	other threads:[~2016-07-21 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 21:11 Tom Tromey
2016-07-12  0:53 ` Manish Goregaokar
2016-07-21 21:14 ` Tom Tromey [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lh0ulmmh.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.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