about summary refs log tree commit diff
diff options
context:
space:
mode:
authorOli Scherer <github35764891676564198441@oli-obk.de>2021-03-15 12:19:29 +0000
committerOli Scherer <github35764891676564198441@oli-obk.de>2021-03-15 12:19:29 +0000
commit1ffd21a15c19121e46f931f44e8442e4a31df236 (patch)
tree96e117b53653f2354e390342d7278c8d8da36fb4
parent9f407ae5ee53a0c1e2ec12ee1087c8f58e5f0ac0 (diff)
downloadrust-1ffd21a15c19121e46f931f44e8442e4a31df236.tar.gz
rust-1ffd21a15c19121e46f931f44e8442e4a31df236.zip
Pacify tidy
-rw-r--r--compiler/rustc_middle/src/ty/consts/valtree.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/rustc_middle/src/ty/consts/valtree.rs b/compiler/rustc_middle/src/ty/consts/valtree.rs
index fbe4c657323..97e7dd6507b 100644
--- a/compiler/rustc_middle/src/ty/consts/valtree.rs
+++ b/compiler/rustc_middle/src/ty/consts/valtree.rs
@@ -11,7 +11,7 @@ use rustc_macros::HashStable;
 /// `AllocId`s point to equal values. So we may end up with different representations for
 /// two constants whose value is `&42`. Furthermore any kind of struct that has padding will
 /// have arbitrary values within that padding, even if the values of the struct are the same.
-/// 
+///
 /// `ValTree` does not have this problem with representation, as it only contains integers or
 /// lists of values of itself.
 pub enum ValTree<'tcx> {