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] fixed indentations in AST pretty expanded dump of trait gcc/rust/ChangeLog:
Date: Sat, 11 Feb 2023 15:30:42 +0000 (GMT)	[thread overview]
Message-ID: <20230211153042.7BB2A3858022@sourceware.org> (raw)

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

commit c02a518fab792e5a8656cc7dfb0b88bb0de8a00f
Author: Abdul Rafey <abdulrafeyq@gmail.com>
Date:   Wed Feb 1 11:02:16 2023 +0530

    fixed indentations in AST pretty expanded dump of trait gcc/rust/ChangeLog:
    
            * ast/rust-ast-dump.cc (Dump::visit): removed extra indentations in trait ast dump
    
    Signed-off-by: Abdul Rafey <abdulrafeyq@gmail.com>

Diff:
---
 gcc/rust/ast/rust-ast-dump.cc | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/gcc/rust/ast/rust-ast-dump.cc b/gcc/rust/ast/rust-ast-dump.cc
index 131e23ea180..7a2fdc5b9b6 100644
--- a/gcc/rust/ast/rust-ast-dump.cc
+++ b/gcc/rust/ast/rust-ast-dump.cc
@@ -1072,8 +1072,6 @@ Dump::visit (TypeBoundWhereClauseItem &item)
 void
 Dump::visit (Method &method)
 {
-  // FIXME: Do we really need to dump the indentation here?
-  stream << indentation;
   visit (method.get_visibility ());
   stream << "fn " << method.get_method_name () << '(';
 
@@ -1326,7 +1324,7 @@ void
 Dump::visit (TraitItemFunc &item)
 {
   auto func = item.get_trait_function_decl ();
-  stream << indentation << "fn " << func.get_identifier () << '(';
+  stream << "fn " << func.get_identifier () << '(';
 
   visit_items_joined_by_separator (func.get_function_params ());
 
@@ -1340,9 +1338,6 @@ Dump::visit (TraitItemMethod &item)
 {
   auto method = item.get_trait_method_decl ();
 
-  // FIXME: Do we really need to dump the indentation here?
-  stream << indentation;
-
   // FIXME: Can we have visibility here?
   // emit_visibility (method.get_visibility ());
   stream << "fn " << method.get_identifier () << '(';

                 reply	other threads:[~2023-02-11 15:30 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=20230211153042.7BB2A3858022@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).