public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "cohenarthur.dev" <cohenarthur.dev@gmail.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: [PATCH] Remove warnings from v0_mangle functions in rust-mangle.cc
Date: Tue, 21 Sep 2021 14:25:20 +0200	[thread overview]
Message-ID: <b86f15bc166a404e761d296504e278a22697fc59.camel@klomp.org> (raw)
In-Reply-To: <20210921115802.wm7gkstjm7wouwst@oneshade>

Hi Arthur,

On Tue, 2021-09-21 at 13:58 +0200, cohenarthur.dev via Gcc-rust wrote:
> I forgot to do a clean build before creating the pull request and the
> file was already compiled... Sorry about that!
> 
> I'll keep on working on v0 mangling in order to get all the parts
> linked correctly, but it was in a bit of a dire state :)

Thanks for working on this. And no worries, I am just allergic to
warnings (I just must look at them to make sure I understand what is
going on and it wasn't me making a mistake).

Cheers,

Mark

      reply	other threads:[~2021-09-21 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 22:49 Mark Wielaard
2021-09-21 11:58 ` cohenarthur.dev
2021-09-21 12:25   ` Mark Wielaard [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=b86f15bc166a404e761d296504e278a22697fc59.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=cohenarthur.dev@gmail.com \
    --cc=gcc-rust@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).