From 5de1fafb1569ad12f039562ca86f14730d970a3b Mon Sep 17 00:00:00 2001 From: Ariel Ben-Yehuda Date: Wed, 18 Sep 2019 19:37:26 +0300 Subject: [PATCH] improve comment --- .../reservation-impls/reservation-impl-non-lattice-ok.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/test/ui/traits/reservation-impls/reservation-impl-non-lattice-ok.rs b/src/test/ui/traits/reservation-impls/reservation-impl-non-lattice-ok.rs index 2517052b5e4..ae1556cb4dc 100644 --- a/src/test/ui/traits/reservation-impls/reservation-impl-non-lattice-ok.rs +++ b/src/test/ui/traits/reservation-impls/reservation-impl-non-lattice-ok.rs @@ -16,10 +16,10 @@ // thing we thought about - see e.g. // https://github.com/rust-lang/rust/issues/57012#issuecomment-452150775 // -// 2. The other way is to notice that `impl From for T` is basically a marker -// trait, as you say since its only method is uninhabited, and allow for "marker -// trait overlap", where the conflict "doesn't matter" as there is nothing that -// can cause a conflict. +// 2. The other way is to notice that `impl From for T` is basically a +// marker trait since its only method is uninhabited, and allow for "marker +// trait overlap", where the conflict "doesn't matter" because it can't +// actually cause any ambiguity. // // Now it turned out lattice specialization doesn't work it, because an // `impl From for Smaht` would require a `impl From for Smaht`, -- 2.44.0