kg
commented
12 years ago Good candidates for things to do here: A 'verbose proxies' mode that lists what classes proxies are applied to, so you can tell when a proxy isn't applying to a class A 'wrong name detection' mode (or default behavior) that spots cases where you used . when you needed to use + or / instead An interactive mode that builds the full type graph but instead of translating an assembly lets you examine the type information
It's pretty easy to end up with a Proxy that looks correct but doesn't actually get used by JSILc. The compiler (or a separate application) should provide some options to let you diagnose why your proxies aren't working and figure out how to fix them.