public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc <dkm@kataplop.net>
To: Mark Wielaard <mark@klomp.org>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: [PATCH 2/2] Remove unused have_more_segments from TypeCheckExpr::resolve_root_path
Date: Wed, 30 Jun 2021 08:54:22 +0200	[thread overview]
Message-ID: <87v95v2675.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <20210629221135.309981-2-mark@klomp.org> (Mark Wielaard's message of "Wed, 30 Jun 2021 00:11:35 +0200")

Mark Wielaard <mark@klomp.org> writes:

> It isn't necessary to know whether there are more segments while
> iteration through the expression segements.

Both patches in GH: https://github.com/Rust-GCC/gccrs/pull/537/commits

Fixed a small typo in the commit message while creating the PR :)

Marc

      reply	other threads:[~2021-06-30  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 22:11 [PATCH 1/2] Remove unused default_ty_param from TypeResolveGenericParam::visit Mark Wielaard
2021-06-29 22:11 ` [PATCH 2/2] Remove unused have_more_segments from TypeCheckExpr::resolve_root_path Mark Wielaard
2021-06-30  6:54   ` Marc [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=87v95v2675.fsf@arrakis.kataplop.net \
    --to=dkm@kataplop.net \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=mark@klomp.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).