No longer calling DeferredTextureImageUsageParams' default ctor.

No longer calling DeferredTextureImageUsageParams' default ctor.

I want to remove SkImage::DeferredTextureImageUsageParams' default ctor.
Before I make that change in Skia, I want to update Chrome to no longer call it.

The default ctor did not initialize all of the members, which lead to surprises.
We could simply initialize all the values to some weird state.
But a better option would be to not allow the object to be created unless it
can be in a valid state.

BUG=2242883004
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Committed: https://crrev.com/7cba2b534ca68449549d7e3a1113c47dd00ec330
Cr-Commit-Position: refs/heads/master@{#415190}

[cblume, 2016-08-27 06:09:04]

Description was changed from

==========
No longer calling DeferredTextureImageUsageParams' default ctor.

I want to remove SkImage::DeferredTextureImageUsageParams' default ctor.
Before I make that change in Skia, I want to update Chrome to no longer call it.

The default ctor did not initialize all of the members, which lead to surprises.
We could simply initialize all the values to some weird state.
But a better option would be to not allow the object to be created unless it
can be in a valid state.


BUG=2242883004
==========

to

==========
No longer calling DeferredTextureImageUsageParams' default ctor.

I want to remove SkImage::DeferredTextureImageUsageParams' default ctor.
Before I make that change in Skia, I want to update Chrome to no longer call it.

The default ctor did not initialize all of the members, which lead to surprises.
We could simply initialize all the values to some weird state.
But a better option would be to not allow the object to be created unless it
can be in a valid state.


BUG=2242883004
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

[cblume, 2016-08-27 06:10:33]

The CQ bit was checked by cblume@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-27 06:11:15]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-27 07:01:28]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-27 07:01:29]

Dry run: This issue passed the CQ dry run.

[cblume, 2016-08-27 07:02:17]

cblume@chromium.org changed reviewers:
+ ericrk@chromium.org

[cblume, 2016-08-27 07:02:18]

PTAL

[ericrk, 2016-08-29 19:39:21]

lgtm

[cblume, 2016-08-29 19:56:06]

The CQ bit was checked by cblume@chromium.org

[cblume, 2016-08-29 20:04:51]

The CQ bit was unchecked by cblume@chromium.org

[cblume, 2016-08-29 20:05:01]

The CQ bit was checked by cblume@chromium.org

[ericrk, 2016-08-29 20:08:39]

The CQ bit was unchecked by ericrk@chromium.org

[ericrk, 2016-08-29 20:08:46]

The CQ bit was checked by ericrk@chromium.org

[commit-bot: I haz the power, 2016-08-29 20:19:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-30 05:58:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-30 06:01:18]

Description was changed from

==========
No longer calling DeferredTextureImageUsageParams' default ctor.

I want to remove SkImage::DeferredTextureImageUsageParams' default ctor.
Before I make that change in Skia, I want to update Chrome to no longer call it.

The default ctor did not initialize all of the members, which lead to surprises.
We could simply initialize all the values to some weird state.
But a better option would be to not allow the object to be created unless it
can be in a valid state.


BUG=2242883004
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
==========

to

==========
No longer calling DeferredTextureImageUsageParams' default ctor.

I want to remove SkImage::DeferredTextureImageUsageParams' default ctor.
Before I make that change in Skia, I want to update Chrome to no longer call it.

The default ctor did not initialize all of the members, which lead to surprises.
We could simply initialize all the values to some weird state.
But a better option would be to not allow the object to be created unless it
can be in a valid state.

BUG=2242883004
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Committed: https://crrev.com/7cba2b534ca68449549d7e3a1113c47dd00ec330
Cr-Commit-Position: refs/heads/master@{#415190}
==========

[commit-bot: I haz the power, 2016-08-30 06:01:19]

Patchset 1 (id:??) landed as
https://crrev.com/7cba2b534ca68449549d7e3a1113c47dd00ec330
Cr-Commit-Position: refs/heads/master@{#415190}