Remove unreachable code.

Remove unreachable code.

BUG=346399
TEST=none

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=173228

[Peter Kasting, 2014-05-01 00:57:56]

Did you instead intend to leave this ASSERT above the return?

[Yoav Weiss, 2014-05-01 06:10:46]

On 2014/05/01 00:57:56, Peter Kasting wrote:
> Did you instead intend to leave this ASSERT above the return?

Yes, the ASSERT should have been before the calculation of result.

[Yoav Weiss, 2014-05-01 06:19:05]

On 2014/05/01 06:10:46, Yoav Weiss wrote:
> On 2014/05/01 00:57:56, Peter Kasting wrote:
> > Did you instead intend to leave this ASSERT above the return?
> 
> Yes, the ASSERT should have been before the calculation of result.

Thanks for fixing it, and apologies for leaving that assert there. 
Do g++/clang have identical "unreached code" warnings? Do the bots look into
that.

LGTM, and thanks again :)

[Peter Kasting, 2014-05-01 20:18:21]

On 2014/05/01 06:19:05, Yoav Weiss wrote:
> On 2014/05/01 06:10:46, Yoav Weiss wrote:
> > On 2014/05/01 00:57:56, Peter Kasting wrote:
> > > Did you instead intend to leave this ASSERT above the return?
> > 
> > Yes, the ASSERT should have been before the calculation of result.

K, I'll move the ASSERT there.

> Do g++/clang have identical "unreached code" warnings? Do the bots look into
> that.

They do, and I hope to eventually turn them on, but there are caveats, e.g. on
Clank it may cost nontrivial build time to do so, which we wouldn't want either.

[Peter Kasting, 2014-05-02 19:08:44]

The CQ bit was checked by pkasting@chromium.org

[commit-bot: I haz the power, 2014-05-02 19:08:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pkasting@chromium.org/268553003/20001

[commit-bot: I haz the power, 2014-05-02 21:11:32]

Change committed as 173228