@Brendan "Those are warnings, but WarnScript was a bad name" --you mean the tools (IDEs, closure compiler, etc) throw warnings, but not the Chrome debugger, for instance, right?
On Fri, Aug 23, 2013 at 2:37 PM, Brendan Eich <[email protected]> wrote: > J B wrote: > >> @Brendan - The typing wouldn't be used at all during run-time. So, unlike >> AS3, it wouldn't check if types were valid, and it wouldn't try an kind of >> implicit coercion. >> >> > Ok, that's not "typing" (I mean not a type system). > > "Those are warnings, but WarnScript was a bad name" - me at JSConf.au last > November. > > The unsoundness means you have something that needs strong tool support, > not just an error or JS console in which to spew. TypeScript got this right. > > This again puts unsound warning "types" outside of the standards track for > a while. But carry on with TypeScript etc. -- TC39 is tracking. > > /be >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
