Use annotations on confuse() functions

Use annotations on confuse() functions

TBR=-floitsch@google.com

Committed: https://github.com/dart-lang/sdk/commit/ec5e0c3d29c47123854499799a132285346b2833

[sra1, 2015-12-09 20:30:12]

Description was changed from

==========
Use annotations on confuse() functions

TBR=-floitsch@google.com
==========

to

==========
Use annotations on confuse() functions

TBR=-floitsch@google.com

Committed:
https://github.com/dart-lang/sdk/commit/ec5e0c3d29c47123854499799a132285346b2833
==========

[sra1, 2015-12-09 20:30:13]

Committed patchset #1 (id:1) manually as
ec5e0c3d29c47123854499799a132285346b2833 (presubmit successful).

[sra1, 2015-12-09 20:33:13]

sra@google.com changed reviewers:
+ floitsch@google.com
- -floitsch@google.com

[floitsch, 2015-12-09 20:40:15]

LGTM with one comment.

https://codereview.chromium.org/1518553002/diff/1/tests/language/const_map2_t...
File tests/language/const_map2_test.dart (right):

https://codereview.chromium.org/1518553002/diff/1/tests/language/const_map2_t...
tests/language/const_map2_test.dart:17: @NoInline() @AssumeDynamic()
I would put them on separate lines, but I really don't mind if they stay the way
they are.

Since we seem to combine @NoInline() and @AssumeDynamic() a lot, it might be
worthwhile adding a new annotation to the test-package (providing both).

https://codereview.chromium.org/1518553002/diff/1/tests/language/range_analys...
File tests/language/range_analysis3_test.dart (right):

https://codereview.chromium.org/1518553002/diff/1/tests/language/range_analys...
tests/language/range_analysis3_test.dart:7: @NoInline() @AssumeDynamic()
Actually the confuse here was still making sure that the return type is an int.