From: Manish Goregaokar <manish@mozilla.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix handling of discriminantless univariant enums in Rust
Date: Sun, 30 Oct 2016 03:36:00 -0000 [thread overview]
Message-ID: <CAFOnWkk0up4VFozB3wCLYPsjkHVzg8BjYuM4fGp9GT2eGXe37w@mail.gmail.com> (raw)
In-Reply-To: <87d1iiwlvx.fsf@tromey.com>
Yes, I'm trying it with the followup patch. I kept them separate since
that's an independent bug that just affects univariant ones too. Will
roll them together.
-Manish
On Sat, Oct 29, 2016 at 8:34 PM, Tom Tromey <tom@tromey.com> wrote:
>>>>>> "Manish" == Manish Goregaokar <manish@mozilla.com> writes:
>
> Manish> `print univariant.a` works for me.
>
> I tried this patch and it failed the way I thought it would:
>
> print univariant.a
> Attempting to access named field a of tuple variant simple::Univariant::Foo, which has only anonymous fields
> (gdb) FAIL: gdb.rust/simple.exp: print univariant.a
>
>
> Maybe you're trying it with the follow-up patch installed?
> In that case I think the patches should probably be combined.
>
> Tom
next prev parent reply other threads:[~2016-10-30 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 23:52 Manish Goregaokar
2016-10-28 19:57 ` Manish Goregaokar
2016-10-30 2:48 ` Tom Tromey
2016-10-30 2:53 ` Tom Tromey
2016-10-30 2:58 ` Manish Goregaokar
2016-10-30 3:06 ` Manish Goregaokar
2016-10-30 3:34 ` Tom Tromey
2016-10-30 3:36 ` Manish Goregaokar [this message]
2016-10-30 3:40 ` Manish Goregaokar
2016-10-31 3:03 ` Tom Tromey
2016-10-31 3:20 ` Manish Goregaokar
2016-10-31 3:29 ` Tom Tromey
2016-10-31 3:47 ` Manish Goregaokar
2016-10-31 6:17 ` Tom Tromey
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=CAFOnWkk0up4VFozB3wCLYPsjkHVzg8BjYuM4fGp9GT2eGXe37w@mail.gmail.com \
--to=manish@mozilla.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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