On 6/1/15, 1:49 PM, "Michael Schmalle" <[email protected]> wrote: > >I was lucky enough to get this info from him as he was trying to talk me >into doing TypeScript.
Ok, thanks for trying. > >But it seems that you guys don't mind sacrificing type correctness on the >arguments in the AS definitions. It still looks like a task to resolve >this >information when creating the as definitions. For me, using Object where multiple types are allowed is good enough for now. I guess that’s a common pattern in JS since they don’t already have classes. Maybe at some point we would allow some way to constrain the types allowed either through ASDoc like Google’s JSDoc or even better, some overloading mechanism. BTW, I dug this up today [1]. Didn’t look to see what is behind these links. But if it is JS, it might be easier for us to parse? -Alex [1] https://code.google.com/p/closure-compiler/wiki/ExternsForCommonLibraries#j Query
