[regexp] fix bogus assertion in CharacterRange constructor.

[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N

Committed: https://crrev.com/d1f68f776eafa62d4bd1cc3465d18c2e47473381
Cr-Commit-Position: refs/heads/master@{#34626}

[Yang, 2016-03-09 12:17:50]

Description was changed from

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.
The solution is to move the check to CharacterRange::Range and
consistently use it across the codebase.t

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N
==========

to

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N
==========

[Yang, 2016-03-09 12:17:57]

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

[commit-bot: I haz the power, 2016-03-09 12:18:03]

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

[commit-bot: I haz the power, 2016-03-09 12:40:53]

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

[commit-bot: I haz the power, 2016-03-09 12:40:54]

Dry run: This issue passed the CQ dry run.

[Jakob Kummerow, 2016-03-09 15:46:43]

lgtm

[Yang, 2016-03-09 15:51:09]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2016-03-09 15:51:18]

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

[commit-bot: I haz the power, 2016-03-09 15:55:01]

Description was changed from

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N
==========

to

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N
==========

[commit-bot: I haz the power, 2016-03-09 15:55:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-09 15:55:41]

Description was changed from

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N
==========

to

==========
[regexp] fix bogus assertion in CharacterRange constructor.

The CharacterRange constructor checks the input for validity. However,
CharacterRange::Singleton also uses the constructor and may have
kEndMarker as input, causing the check to fail.

The solution is to move the check to CharacterRange::Range and
consistently use it across the code base.

R=jkummerow@chromium.org
BUG=chromium:593282
LOG=N

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

[commit-bot: I haz the power, 2016-03-09 15:55:42]

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