Skip to content
This repository has been archived by the owner on Feb 22, 2018. It is now read-only.

compiler doesn't understand linkage of dart.dynamic, void, bottom #417

Closed
jmesserly opened this issue Jan 21, 2016 · 3 comments
Closed

compiler doesn't understand linkage of dart.dynamic, void, bottom #417

jmesserly opened this issue Jan 21, 2016 · 3 comments
Assignees

Comments

@jmesserly
Copy link
Contributor

After CL 6c1c940 it is no longer safe for the compiler to assume dart.dynamic is a valid JS expression to instantiate it.

Instead the compiler needs to understand that dynamic is a first class reference to the Type for dynamic, and know what Element corresponds to that type declaration, so it can be generated in the correct order.

@jmesserly
Copy link
Contributor Author

in general all "dart." references are problematic now. We need to instead go through _emitTypeName. The good news is we can probably eliminate special case code we have for these types.

@jmesserly
Copy link
Contributor Author

Oh shoot. So it's easy to fix, but I blundered into #257. Taking a look at that now.

@jmesserly
Copy link
Contributor Author

This is fixed now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant