Check if enclosingElement is null.

sdk/lib/_internal/compiler/implementation/resolution/members.dart

Index: sdk/lib/_internal/compiler/implementation/resolution/members.dart
diff --git a/sdk/lib/_internal/compiler/implementation/resolution/members.dart b/sdk/lib/_internal/compiler/implementation/resolution/members.dart
index 7f8681001974c2c19c425430c9b2b16ec3883260..beb5348e2875c8c23cc21129ef64476cb6a85ef3 100644
--- a/sdk/lib/_internal/compiler/implementation/resolution/members.dart
+++ b/sdk/lib/_internal/compiler/implementation/resolution/members.dart
@@ -1638,7 +1638,8 @@ class ResolverVisitor extends CommonResolverVisitor<Element> {
       typeResolver = new TypeResolver(compiler),
       scope = element.buildScope(),
       inCheckContext = compiler.enableTypeAssertions &&

[ngeoffray, 2013/03/01 09:49:18]

Comment?

[karlklose, 2013/03/01 10:21:44]

Created a CL.

-          !element.enclosingElement.isTypedef(),
+          (element.enclosingElement == null ||
+           !element.enclosingElement.isTypedef()),

[ngeoffray, 2013/03/01 09:49:18]

So we're creating a ResolverVisitor for things contained in a Typedef? What are
those? Parameters, type parameters? This looks kind of odd.

[ahe, 2013/03/01 09:54:36]

I'm also confused about this. This fix does not look right to me.

[karlklose, 2013/03/01 10:21:44]

When the signature resolver asks the VariableListElement of the typdef for its
type, the creates a ResolverVisitor to call resolveReturnType.

[ahe, 2013/03/12 08:15:40]

That does not explain why you have an element that does not have an enclosing
element here.

       inCatchBlock = false,
       super(compiler);