New analyzer snapshot.

New analyzer snapshot.

1. Rename WorkManagerPriority -> SourcePriority.

2. Replace CharSequence with String.


R=brianwilkerson@google.com
BUG=

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

[Brian Wilkerson, 2014-02-06 18:08:03]

LGTM

[scheglov, 2014-02-06 18:09:35]

Committed patchset #1 manually as r32373 (presubmit successful).

[blois, 2014-02-13 01:08:40]

https://codereview.chromium.org/156763002/diff/1/pkg/observe/lib/transformer....
File pkg/observe/lib/transformer.dart (left):

https://codereview.chromium.org/156763002/diff/1/pkg/observe/lib/transformer....
pkg/observe/lib/transformer.dart:119: var reader = new CharSequenceReader(new
CharSequence(code));
Note that the pubspec.yaml for observe is still <0.12. Ditto for Polymer.

[Siggi Cherem (dart-lang), 2014-02-13 01:25:21]

https://codereview.chromium.org/156763002/diff/1/pkg/observe/lib/transformer....
File pkg/observe/lib/transformer.dart (left):

https://codereview.chromium.org/156763002/diff/1/pkg/observe/lib/transformer....
pkg/observe/lib/transformer.dart:119: var reader = new CharSequenceReader(new
CharSequence(code));
On 2014/02/13 01:08:41, blois wrote:
> Note that the pubspec.yaml for observe is still <0.12. Ditto for Polymer.

Good catch Pete. Yeah, this should bump up the version constraint on observe.
While this is not a breaking change for observe, the pubspec of should reflect
that it now depends on the new analyzer. Also note that because the next version
of observe will be used with the next version of polymer, we should make sure
that their dependencies are also consistent with each other (otherwise pub will
fail to find a solution).

Thinking more about this, probably every time we increase the version of a
package in the repo, we should consider updating the constraints on every
project that depends on it (and possibly repeat the process if we have to bump
the versions on those packages too).