Hashcodes were being improperly calculated for public API of libraries.

compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart

Index: compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart
diff --git a/compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart b/compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart
index e255a53ceab04571b3a172c0f7ac520e65763505..2773973eb4507a5013338e4724f4e2c3550dd78b 100644
--- a/compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart
+++ b/compiler/javatests/com/google/dart/compiler/end2end/inc/my.no5ref.dart
@@ -48,3 +48,14 @@ class Foo extends Other2 {
 // Reference Other4 using it as a type parameter bound.
 class Bar<T extends Other4> {
 }
+
+// Test against normalization affecting hashcodes

[jbrosenberg, 2011/10/11 14:58:44]

I'm not sure how this tests against normalization affecting things?

[codefu, 2011/10/11 18:43:55]

Recap of conversation:
Interface gets default constructor "(){}" added at normalization. Anything
depending on that interface will have a hashcode mismatch between that libraries
'.deps' file and the API of the interface's library.  Just implementing the
interface here would only cause this file to recompile.  Implementing the
interface in another lib and depending on it will cause both files to re-parse
and re-compile when any file in 'my.app.dart' is touched.

+// SomeInterface2 is the interface that gets the default constructor injected
+// by the dartc backend.  Just implementing that interface here would only
+// cause a hash inconsistency in this file and we'd only compile this one.
+// By depending on a class that implements the interface in a different
+// file (SomeClass2), we'll see that class fail its hash check and two files be
+// recompiled every time this file is modified.
+class Baz {
+  SomeClass2 sc2;
+}