Fix try/poi/serialize_test after adding class to dart:core.

Fix try/poi/serialize_test after adding class to dart:core.

Committed: https://code.google.com/p/dart/source/detail?r=41655

[Lasse Reichstein Nielsen, 2014-11-11 09:02:32]

lrn@google.com changed reviewers:
+ ricow@google.com

[Lasse Reichstein Nielsen, 2014-11-11 09:02:33]

TBR

[Lasse Reichstein Nielsen, 2014-11-11 09:02:54]

Committed patchset #2 manually as r41655 (presubmit successful).

[ricow1, 2014-11-11 09:04:27]

ricow@google.com changed reviewers:
+ ahe@google.com

[ricow1, 2014-11-11 09:04:28]

Move ahe@ to reviewer, move me to cc, I don't know anything about this

[ahe, 2014-11-11 09:14:47]

LGTM

Don't forget to announce this breaking change.

[Lasse Reichstein Nielsen, 2014-11-11 09:24:48]

On 2014/11/11 09:14:47, ahe wrote:
> LGTM
> 
> Don't forget to announce this breaking change.

Ack, will do.

It should only be breaking if you depend on the exact toString of a RangeError,
or if you use runtimeType. I don't think we have generally guaranteed to not
change the runtimeType.

[ahe, 2014-11-11 09:29:50]

On 2014/11/11 09:24:48, Lasse Reichstein Nielsen wrote:
> On 2014/11/11 09:14:47, ahe wrote:
> > LGTM
> > 
> > Don't forget to announce this breaking change.
> 
> Ack, will do.
> 
> It should only be breaking if you depend on the exact toString of a
RangeError,
> or if you use runtimeType. I don't think we have generally guaranteed to not
> change the runtimeType.

Also, if you have something like this:

class SuperInLibraryA {
  IndexError() { // Yeah, I'm not following the Dart style guide.
  }
}

class ClassInLibraryB extends SuperInLibraryA {
  m() => IndexError();
}

Regardless, I question the reasoning behind adding more exception/error classes
to dart:core. They serve exactly no purpose and only make more co19 tests, and
make dart2js output larger.