Test specializations - #782
Conversation
process_results is as of now tested separately because the corresponding iterator is not exposed nicely, and because it is not `Clone`. However, the respective tests already diverged. Instead of fixing process_results, we should strive to uniformly use test_specializations for ProcessResults, too.
|
I worked some time ago on a (maybe too complex) way to test specializations (draft: #756 (comment)) before I split focus on other things. |
|
@Philippe-Cholet Can you merge this? I‘ll raise the limit to ten when I have time. Side note: tbh I just filed this as a PR to have the CI/Tests/Checks running, but it seems I cannot merge myself anymore (as it was the case back then with bors). Am I doing something wrong? |
|
@phimuemue All the maintainer part is new to me but I guess we can not merge a PR (except jswrenn I suppose as he is an owner) especially if it has a commit we wrote without explicit approval, something like that. I think it would have work if you approved your own changes. |
3 participants
We have more and more specializations, but so far they are not vastly tested for iterators that have already been advanced. This PR alters
test_specializations.