Uh oh!
There was an error while loading. Please reload this page.
[MIR] Change SimplifyCfg pass to use BitVec - #31447
Conversation
rust-highfive
commented
Feb 6, 2016
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
55003d9 to
950e58aComparebors
commented
Feb 9, 2016
☔ The latest upstream changes (presumably #31425) made this pull request unmergeable. Please resolve the merge conflicts. |
950e58a to
ebb5b7aComparebors
commented
Feb 18, 2016
☔ The latest upstream changes (presumably #31600) made this pull request unmergeable. Please resolve the merge conflicts. |
bluss
commented
Feb 19, 2016
This was briefly discussed here #30238 (comment), merely some guesses on how big the dataset really is, and what's the appropriate fix. BitVec seems better than Vec either way. |
BitVector is much more space efficient.
ebb5b7a to
b92e243Comparenagisa
commented
Feb 23, 2016
Rebased. This is a pretty simple one and independent from others so could land right now. |
| type Item = usize; | ||
| fn next(&mut self) -> Option<usize> { | ||
| while self.current == 0 { | ||
| self.current = if let Some(&i) = self.iter.next() { |
There was a problem hiding this comment.
It seems like it'd be easier/clearer to just keep a slice with some indices here.
There was a problem hiding this comment.
(But don't feel you have to change it.)
nikomatsakis
commented
Feb 23, 2016
@bors r+ |
bors
commented
Feb 23, 2016
📌 Commit b92e243 has been approved by |
bors
commented
Feb 23, 2016
BitVector is more space efficient.
BitVector is more space efficient.