-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Updates to Ranges test machinery #959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This manages to both look great and create a terrible headache for all the coming merge conflicts |
@StephanTLavavej has been calling me "Merge Conflict" for years now. |
|
Back when @BillyONeal and @CaseyCarter were in the same office, and were constantly submitting PRs with merge conflicts against each other, I placed a sticky note over their office nameplate, dubbing them Billy "Merge" O'Neal and Casey "Conflict" Carter. 😹 |
* The point is to break the abstraction and provide access to the internal pointer. There's no reason to mimic the behavior of iterator/sentinel adaptors, it just makes the test tool harder to use. * Enforce that `begin` is called at most once in `test::range::_Unchecked_begin` * Remove default arguments to the `test_meow` functions in `<range_algorithm_support.hpp>`.
|
Thanks for making it easier to test ranges! |
Replace
basemember oftest::iteratorandtest::sentinelwithpeek. The point is to break the abstraction and provide access to the internal pointer. There's no reason to mimic the behavior of iterator/sentinel adaptors, it just makes the test tool harder to use.test::range::beginenforces the restriction that it may be called at most once for a single-pass range.test::range::_Unchecked_beginshould be subject to the same restriction.Remove default template arguments for the element types of ranges in the instantiation helpers (
test_in,test_fwd_fwd, etc.) forcing the element types to be explicitly specified.