You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C-bugCategory: This is a bug.I-unsoundIssue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/SoundnessT-libsRelevant to the library team, which will review and decide on the PR/issue.
While playing around with VecDeque, I encountered what seems to be a rather specific bug with the following code (if you're wondering, it's related to day 22 from Advent of Code):
As far as I understand, the last line should always be true, and in fact if I comment out v.make_contiguous() or if I insert the elements in a different order, or if I insert one value less, or one value more, this works totally fine.
However, when the VecDeque is in this specific configuration, the back of the vector is equal to 43, instead of 11.
Mark-Simulacrum
added
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
and removed
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
labels
Dec 23, 2020
C-bugCategory: This is a bug.I-unsoundIssue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/SoundnessT-libsRelevant to the library team, which will review and decide on the PR/issue.
Hi!
While playing around with VecDeque, I encountered what seems to be a rather specific bug with the following code (if you're wondering, it's related to day 22 from Advent of Code):
As far as I understand, the last line should always be true, and in fact if I comment out
v.make_contiguous()
or if I insert the elements in a different order, or if I insert one value less, or one value more, this works totally fine.However, when the
VecDeque
is in this specific configuration, the back of the vector is equal to43
, instead of11
.Meta
rustc --version --verbose
:I've also run this in the playground in both beta and nightly but the code works fine then.
Backtrace
The text was updated successfully, but these errors were encountered: