<p dir="auto">This is a tracking issue for the unstable <code class="notranslate">str_parse_error</code> and <code class="notranslate">utf8_error</code> features in the standard library. Some various small error types popped up once <code class="notranslate">FromStr</code> had an associated error type and haven't been considered too closely for stabilization.</p>
<p dir="auto">Some thoughts are:</p>
<ul dir="auto">
<li>Are the names of these types appropriate?</li>
<li>Are we covered in terms of future extensibility?</li>
<li>Are the relevant portions of the error exposed well?</li>
</ul>
<p dir="auto">I'm in the finishing touches of adding a <code class="notranslate">container::MutableSeq</code>, and I'm realizing it's a bit inconsistent that <code class="notranslate">vec</code> has methods like <code class="notranslate">push()</code> whereas <code class="notranslate">DList</code> has <code class="notranslate">push_back()</code>. I personally feel that we should rename the vec methods to make it explicit where exactly we are pushing/popping the values. I suggest that we make these following renames:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content=".push() =&gt; .push_back()
.pop() =&gt; .pop_back()
.unshift() =&gt; .push_front()
.shift() =&gt; .pop_front()"><pre class="notranslate"><code class="notranslate">.push() =&gt; .push_back()
.pop() =&gt; .pop_back()
.unshift() =&gt; .push_front()
.shift() =&gt; .pop_front()
</code></pre></div>
<p dir="auto">We could also use <code class="notranslate">append()</code> and <code class="notranslate">prepend()</code> for <code class="notranslate">push()</code> and <code class="notranslate">pop()</code>, but I don't like that as much. Or we could rename the DList methods, but I'm also not in favor of that. What does everyone else think?</p>