Optional Strong Typing

J B port25 at gmail.com
Fri Aug 23 12:50:36 PDT 2013


@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 <brendan at mozilla.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130823/8b05ce8d/attachment-0001.html>


More information about the es-discuss mailing list