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] Fix formatting Date: Wed, 8 Jun 2022 10:44:16 +0000 (GMT) [thread overview] Message-ID: <20220608104416.32FC33858C27@sourceware.org> (raw) https://gcc.gnu.org/g:4b995062b737d0cdf3008f8d84af8526904de3b1 commit 4b995062b737d0cdf3008f8d84af8526904de3b1 Author: Yizhe <yizhe@pku.edu.cn> Date: Wed Mar 17 09:22:15 2021 +0000 Fix formatting Diff: --- gcc/rust/ast/rust-expr.h | 2 +- gcc/rust/util/rust-make-unique.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/rust/ast/rust-expr.h b/gcc/rust/ast/rust-expr.h index b535f8f36b1..db900966ce6 100644 --- a/gcc/rust/ast/rust-expr.h +++ b/gcc/rust/ast/rust-expr.h @@ -1116,7 +1116,7 @@ public: inner_attrs (other.inner_attrs), locus (other.locus), marked_for_strip (other.marked_for_strip) { - internal_elements = other.internal_elements->clone_array_elems (); + internal_elements = other.internal_elements->clone_array_elems (); rust_assert (internal_elements != nullptr); } diff --git a/gcc/rust/util/rust-make-unique.h b/gcc/rust/util/rust-make-unique.h index 0c4da2fb6c2..4698b7d966f 100644 --- a/gcc/rust/util/rust-make-unique.h +++ b/gcc/rust/util/rust-make-unique.h @@ -7,7 +7,7 @@ namespace Rust { template <typename T, typename... Ts> std::unique_ptr<T> -make_unique (Ts &&...params) +make_unique (Ts &&... params) { return std::unique_ptr<T> (new T (std::forward<Ts> (params)...)); }
next reply other threads:[~2022-06-08 10:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-08 10:44 Thomas Schwinge [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-03-05 11:40 Thomas Schwinge 2022-06-08 10:46 Thomas Schwinge 2022-06-08 10:39 Thomas Schwinge
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=20220608104416.32FC33858C27@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: linkBe 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).