| commit | b9df230d65e93e1ba31cd1e677d82b885cb59f6f | [log] [tgz] |
|---|---|---|
| author | Mike Klein <mtklein@google.com> | Tue Nov 19 13:35:42 2019 -0600 |
| committer | Skia Commit-Bot <skia-commit-bot@chromium.org> | Tue Nov 19 21:06:10 2019 +0000 |
| tree | 03e21d70e0362cc3573e63048d191da224f0d5f9 | |
| parent | 30a35e83b104cd50c8267440c4ec38771745aba6 [diff] |
initialize to avoid Valgrind false positive I don't think it makes things any slower, less clear, or less safe to initialize this `isClosed` variable. I'd be inclined to leave it this way even if hypothetically we roll to a newer Valgrind that can analyze this correctly. For background see https://internals.rust-lang.org/t/valgrind-memcheck-false-positive-fixes-for-rust/11166 Change-Id: Ifef9417733824b857d4407c45c92c017d189a8fa Reviewed-on: https://skia-review.googlesource.com/c/skia/+/255354 Commit-Queue: Mike Klein <mtklein@google.com> Commit-Queue: Brian Salomon <bsalomon@google.com> Auto-Submit: Mike Klein <mtklein@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com>