<p dir="auto">Here is the illustrative example:</p>
<div class="highlight highlight-source-rust notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="fn foo() {
    { bar('}'); }
    { bar(']'); }
    { bar(')'); }
}"><pre class="notranslate"><span class="pl-k">fn</span> <span class="pl-en">foo</span><span class="pl-kos">(</span><span class="pl-kos">)</span> <span class="pl-kos">{</span>
    <span class="pl-kos">{</span> <span class="pl-en">bar</span><span class="pl-kos">(</span><span class="pl-s">'}'</span><span class="pl-kos">)</span><span class="pl-kos">;</span> <span class="pl-kos">}</span>
    <span class="pl-kos">{</span> <span class="pl-en">bar</span><span class="pl-kos">(</span><span class="pl-s">']'</span><span class="pl-kos">)</span><span class="pl-kos">;</span> <span class="pl-kos">}</span>
    <span class="pl-kos">{</span> <span class="pl-en">bar</span><span class="pl-kos">(</span><span class="pl-s">')'</span><span class="pl-kos">)</span><span class="pl-kos">;</span> <span class="pl-kos">}</span>
<span class="pl-kos">}</span></pre></div>
<p dir="auto">The characters within <code class="notranslate">'</code> characters above are incorrectly treated by <code class="notranslate">src/etc/rust-mode.el</code> as closing the opening paren of the invocation of <code class="notranslate">bar</code>.  This confuses Emacs in a number of ways (e.g. obviously paren matching; but also the auto-indentation gets confused too, which is more annoying).</p>
<p dir="auto">The new path code has a bunch of duplicate code between the posix and windows variants. It should be factored into material in the abstract Path trait, when default methods work.</p>