Closed autoantwort closed 2 months ago
@autoantwort We typically create issues and discuss them before creating PRs. I see many small PRs from you (which is overwhelming), and their motivation is not clear. My suggestion is to create one PR with all small fixes/cleanups, and we can later discuss these together. For the time being, I will close the PRs that have been open.
So you prefer one big PR with many unrelated changes instead of one PR per concern? Should I create one Issue for every PR / Concern or one Big one?
I suggest discussing the problem first. We want to understand the motivation before reviewing the PRs. Many PRs appeared very small. You can create an issue for each separate problem. A PR can afterwards be created for multiple issues.
I have created #770
.begin()
could return an iterator object depending on the build context