| commit | f2c5add463f5fbb425934ef71390ca848a9df01a | |
| author | mdempsky <mdempsky@chromium.org> | |
| Mon, 15 Dec 2014 23:26:13 +0000 (15 15:26 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Mon, 15 Dec 2014 23:26:44 +0000 (15 23:26 +0000) | ||
| tree | e74f5374b7d660ed9253bbfb9bffe9c0716cdfca | treesnapshot (tar.gz zip) |
| parent | 590871bd9bff6699b46a207272cd62fbd0dece01 | commitdiff |
tuple: leave fields uninitialized in default constructors
Using "x()" in TupleLeaf's default constructor causes primitive types
(e.g., integers and pointers) to be zero initialized, whereas
previously Tuple left them indeterminate. Arguably zero-initializing
is better, but the change was inadvertant and results in a measurable
code size increase, so this CL reverts it (at least for now).
BUG=440806
Review URL: https://codereview.chromium.org/791883003
Cr-Commit-Position: refs/heads/master@{#308455}
Using "x()" in TupleLeaf's default constructor causes primitive types
(e.g., integers and pointers) to be zero initialized, whereas
previously Tuple left them indeterminate. Arguably zero-initializing
is better, but the change was inadvertant and results in a measurable
code size increase, so this CL reverts it (at least for now).
BUG=440806
Review URL: https://codereview.chromium.org/791883003
Cr-Commit-Position: refs/heads/master@{#308455}
| base/tuple.h | diffblobblamehistory |