[SPv2] Remove PaintArtifactCompositor::initializeIfNeeded.

[SPv2] Remove PaintArtifactCompositor::initializeIfNeeded.

Now that we can guarantee the RuntimeEnabledFeatures is initialized in the
constructor, it seems like a cleaner place to put this kind of mandatory
initialization logic.

The only caveat is that the constructor will be called when SPv2 is off, but
that's easily handled by changing an assert to a conditional return.

BUG=563667
Committed: https://crrev.com/e502046d370b3f3c77e91dab787c97e21ff9c27d
Cr-Commit-Position: refs/heads/master@{#376349}

[jbroman, 2016-02-17 19:10:31]

jbroman@chromium.org changed reviewers:
+ pdr@chromium.org

[jbroman, 2016-02-17 19:10:32]

not important, but I forgot to fully kill the two-phase initialization in this
class, so why not?

[pdr., 2016-02-18 21:20:08]

On 2016/02/17 at 19:10:32, jbroman wrote:
> not important, but I forgot to fully kill the two-phase initialization in this
class, so why not?

LGTM

[jbroman, 2016-02-18 21:26:42]

The CQ bit was checked by jbroman@chromium.org

[commit-bot: I haz the power, 2016-02-18 21:28:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1705863002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1705863002/1

[commit-bot: I haz the power, 2016-02-18 21:51:49]

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

[commit-bot: I haz the power, 2016-02-18 21:51:50]

Try jobs failed on following builders:
  linux_chromium_compile_dbg_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jbroman, 2016-02-18 22:18:56]

The CQ bit was checked by jbroman@chromium.org

[commit-bot: I haz the power, 2016-02-18 22:20:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1705863002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1705863002/1

[commit-bot: I haz the power, 2016-02-19 01:14:42]

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

[commit-bot: I haz the power, 2016-02-19 01:14:43]

Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[jbroman, 2016-02-19 01:34:21]

The CQ bit was checked by jbroman@chromium.org

[commit-bot: I haz the power, 2016-02-19 01:38:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1705863002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1705863002/1

[commit-bot: I haz the power, 2016-02-19 02:40:25]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-19 02:41:14]

Description was changed from

==========
[SPv2] Remove PaintArtifactCompositor::initializeIfNeeded.

Now that we can guarantee the RuntimeEnabledFeatures is initialized in the
constructor, it seems like a cleaner place to put this kind of mandatory
initialization logic.

The only caveat is that the constructor will be called when SPv2 is off, but
that's easily handled by changing an assert to a conditional return.

BUG=563667
==========

to

==========
[SPv2] Remove PaintArtifactCompositor::initializeIfNeeded.

Now that we can guarantee the RuntimeEnabledFeatures is initialized in the
constructor, it seems like a cleaner place to put this kind of mandatory
initialization logic.

The only caveat is that the constructor will be called when SPv2 is off, but
that's easily handled by changing an assert to a conditional return.

BUG=563667

Committed: https://crrev.com/e502046d370b3f3c77e91dab787c97e21ff9c27d
Cr-Commit-Position: refs/heads/master@{#376349}
==========

[commit-bot: I haz the power, 2016-02-19 02:41:16]

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