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 #1164
Date: Wed,  8 Jun 2022 12:37:37 +0000 (GMT)	[thread overview]
Message-ID: <20220608123737.B16CB381A7D1@sourceware.org> (raw)

https://gcc.gnu.org/g:b74044fb6278e373da607a8f1f5df2193ce27d65

commit b74044fb6278e373da607a8f1f5df2193ce27d65
Merge: 2b1cb4ba869 d0c75495dda
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Apr 25 19:14:00 2022 +0000

    Merge #1164
    
    1164: Add `NodeId`s to `SimplePath{Segment}`s r=CohenArthur a=CohenArthur
    
    This is a necessary first step which addresses #1158
    
    I am working on the visibility resolver and simple-path name resolver in parallel and will need those changes.
    
    I'm not sure if the `has_path` method is necessary since we will have `HIR::Visibilities` in the visibility resolver, which will be desugared. Maybe I am doing this wrong and we should be working on `AST::Visibilities` instead?
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/ast/rust-ast.h  | 10 ++++++++--
 gcc/rust/ast/rust-item.h |  3 +++
 2 files changed, 11 insertions(+), 2 deletions(-)


                 reply	other threads:[~2022-06-08 12:37 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=20220608123737.B16CB381A7D1@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).