diff options
| author |  Mike Klein <mtklein@chromium.org> | 2018-04-19 09:18:33 -0400 |
|---|---|---|
| committer |  Skia Commit-Bot <skia-commit-bot@chromium.org> | 2018-04-19 13:57:44 +0000 |
| commit | cc9856cdd51fa9530496d8080cf84997838314a9 (patch) | |
| tree | c2e9dbf018106839edd2153e7dc0b4af4ffca3a3 /src/core/SkScan_AAAPath.cpp | |
| parent | e7fd7ff0eca868c35eccb7a870fbc7bc05aa9176 (diff) | |
clean up setReserve() rule-bending
These routines call setReserve(N), write M<N items into the reserved
memory, and then setCount(M) afterwards. That happens to function with
SkTDArray's current implementation, but really breaks the spirit of what
setReserve() means.
This CL switches those setReserve() calls to setCount().
Calling setCount(N), writing M<N items, then setCount(M) should have the
exact same effect, and be completely within the rules.
Already reviewed here: https://skia-review.googlesource.com/c/skia/+/115982
Change-Id: I462479488055cf1c99de2bc6dbc1707dbe24db7e
Reviewed-on: https://skia-review.googlesource.com/122301
Reviewed-by: Mike Klein <mtklein@chromium.org>
Reviewed-by: Brian Osman <brianosman@google.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Commit-Queue: Brian Osman <brianosman@google.com>
Auto-Submit: Mike Klein <mtklein@chromium.org>
Diffstat (limited to 'src/core/SkScan_AAAPath.cpp')
0 files changed, 0 insertions, 0 deletions