<p dir="auto"><a href="http://doc.rust-lang.org/nightly/std/primitive.f32.html" rel="nofollow"><code class="notranslate">std::f32</code></a> doc page has <code class="notranslate">impl Float for f32</code> at the top and at the bottom.</p>
<ul dir="auto">
<li>The bottom one seems to have more elements though it's not clear why.</li>
<li>Their styling is the same so it's not obvious if they should mean 2 different things.</li>
</ul>
<p dir="auto">Something should change so either they don't look like misshapen clones or it's clear what they mean.</p>
<p dir="auto">Here's an example I just got:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="src/anthill/execution/kind.rs:124:32: 125:29 error: cannot infer an appropriate lifetime due to conflicting requirements
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
src/anthill/execution/kind.rs:125                             };
src/anthill/execution/kind.rs:124:32: 124:55 note: first, the lifetime cannot outlive the expression at 124:32...
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~
src/anthill/execution/kind.rs:124:32: 124:55 note: ...due to the following expression
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~
src/anthill/execution/kind.rs:124:32: 125:29 note: but, the lifetime must be valid for the method call at 124:32...
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
src/anthill/execution/kind.rs:125                             };
src/anthill/execution/kind.rs:124:32: 124:55 note: ...due to the following expression
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~"><pre class="notranslate"><code class="notranslate">src/anthill/execution/kind.rs:124:32: 125:29 error: cannot infer an appropriate lifetime due to conflicting requirements
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
src/anthill/execution/kind.rs:125                             };
src/anthill/execution/kind.rs:124:32: 124:55 note: first, the lifetime cannot outlive the expression at 124:32...
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~
src/anthill/execution/kind.rs:124:32: 124:55 note: ...due to the following expression
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~
src/anthill/execution/kind.rs:124:32: 125:29 note: but, the lifetime must be valid for the method call at 124:32...
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
src/anthill/execution/kind.rs:125                             };
src/anthill/execution/kind.rs:124:32: 124:55 note: ...due to the following expression
src/anthill/execution/kind.rs:124                                 dictionary.name_to_kind.find(&amp;name)
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~
</code></pre></div>
<p dir="auto">Now, I'm developing some experience with lifetimes so I have some intuition about what I did wrong. And I appreciate the effort that went into this error message! But still, saying "the lifetime can't outlive the expression X in location Y because it must be valid at the function call at exactly the same expression X in the same location Y" - that's not exactly explaining things in a way that is understandable to a newcomer (which I still am).</p>
<p dir="auto">Perhaps there's a better way to phrase the problem, and possibly eliminate the duplications?</p>