Details
- Reviewers
var-const philnik ldionne - Group Reviewers
Restricted Project - Commits
- rG594fa1474f0c: [libc++][ranges] implement `std::ranges::drop_while_view`
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/include/__ranges/drop_while_view.h | ||
---|---|---|
68 | Maybe that's a bit better for a user? Per live review, we think that's the only situation that can lead us to this assertion failing. Also, this is non-blocking because extremely pedantic, but it might be nice to add an assert.<xxxxxx>.pass.cpp test to check that behavior. You can take inspiration of other tests like libcxx/test/libcxx/strings/basic.string/string.access/assert.back.pass.cpp. | |
libcxx/test/std/ranges/range.adaptors/range.drop.while/ctor.default.pass.cpp | ||
17 | Same below. | |
19–22 | Maybe you could initialize i to a non-zero value just to rule out the fact that we're accessing zeroed-by-chance memory that would be uninitialized below? | |
libcxx/test/std/ranges/range.adaptors/range.drop.while/general.pass.cpp | ||
20 | Maybe that's closer to what a user would actually write? |
Maybe that's a bit better for a user? Per live review, we think that's the only situation that can lead us to this assertion failing.
Also, this is non-blocking because extremely pedantic, but it might be nice to add an assert.<xxxxxx>.pass.cpp test to check that behavior. You can take inspiration of other tests like libcxx/test/libcxx/strings/basic.string/string.access/assert.back.pass.cpp.