public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #900
Date: Wed,  8 Jun 2022 12:02:45 +0000 (GMT)	[thread overview]
Message-ID: <20220608120245.292103AA9812@sourceware.org> (raw)

https://gcc.gnu.org/g:6e5f8f76cbe47880ceae1bcf0bf7f07f601517ec

commit 6e5f8f76cbe47880ceae1bcf0bf7f07f601517ec
Merge: 631f7ae7b9d 4c36c7c8d31
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Jan 31 15:26:53 2022 +0000

    Merge #900
    
    900: Fixup logic in canonical-path for impl-blocks r=philberty a=philberty
    
    Impl blocks canonical prefix when the size is one will only contain the
    respective crate name but impl blocks canonical path will be of the Self
    type which has its own respective crate and path so this will become the
    canonical path of this. If the segment size greater than one this means it
    is likely inside a mod block or other item so this means we should just
    append as usual.
    
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/resolve/rust-ast-resolve-item.h | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)


                 reply	other threads:[~2022-06-08 12:02 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=20220608120245.292103AA9812@sourceware.org \
    --to=tschwinge@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: 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).