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 #1191
Date: Wed,  8 Jun 2022 12:42:01 +0000 (GMT)	[thread overview]
Message-ID: <20220608124201.D1E81386CE63@sourceware.org> (raw)

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

commit fb136314f9584744ccc7b09ace3cea99129b7cf4
Merge: 27e562a2c07 98e1de2d8fd
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon May 2 14:32:12 2022 +0000

    Merge #1191
    
    1191: Resolve simple paths in use items r=CohenArthur a=CohenArthur
    
    In order to resolve `SimplePath`s, we have to expand all paths present
    in a `UseDeclaration` and resolve them. For example, we want to resolve
    two paths with the following statement `use foo::bar::{baz, bul}`:
    `foo::bar::baz` and `foo::bar::bul`
    This also removes the prelude inclusion (`use std::prelude::v1::*`)
    since we cannot resolve it (yet!)
    
    Needs #1172 to compile
    Adresses #1159
    Adresses #1187
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/ast/rust-ast.h                        |   2 +
 gcc/rust/ast/rust-item.h                       |  57 +++++
 gcc/rust/resolve/rust-ast-resolve-item.cc      | 297 ++++++++++++++++++++++++-
 gcc/rust/resolve/rust-ast-resolve-item.h       |  11 +
 gcc/rust/resolve/rust-ast-resolve-type.cc      |  47 ++++
 gcc/rust/resolve/rust-ast-resolve-type.h       |  55 +----
 gcc/rust/rust-lang.cc                          |   2 +
 gcc/rust/rust-session-manager.cc               |  36 +--
 gcc/testsuite/rust/compile/torture/cfg_attr.rs |   2 +-
 gcc/testsuite/rust/compile/use_1.rs            |  16 ++
 10 files changed, 455 insertions(+), 70 deletions(-)


                 reply	other threads:[~2022-06-08 12:42 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=20220608124201.D1E81386CE63@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).